enso/docs
Dmitry Bushev 670cffb380
Fix Storing the Runtime Types (#1271)
A bunch of improvements to the suggestions
system. Suggestions are extracted to the tree data
structure. The tree allows producing better diffs
between the file versions. And better diffs reduce
the number of updates that are sent to the IDE
after a file change, and consequently fix the
issue when the runtime type got overwritten with
the compile-time type.
2020-11-10 14:50:37 +03:00
..
debugger Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00
distribution Initial Legal Review (#1210) 2020-10-19 10:50:12 +02:00
infrastructure Separate ComponentManager from Launcher (#1248) 2020-10-30 12:31:31 +01:00
language-server Fix Storing the Runtime Types (#1271) 2020-11-10 14:50:37 +03:00
parser Create the initial design for the macro system (#1264) 2020-11-03 10:07:54 +00:00
polyglot Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00
rfcs Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00
runtime Opt-in TCO (#1219) 2020-10-15 16:52:26 +02:00
semantics Opt-in TCO (#1219) 2020-10-15 16:52:26 +02:00
style-guide Implement Launcher Self-Update (#1125) 2020-09-09 15:37:26 +02:00
syntax Complete the implementation of the Enso lexer (#1177) 2020-10-30 14:06:24 +00:00
types Restructure the Standard Library (#1245) 2020-10-29 08:48:48 +03:00
CODE_OF_CONDUCT.md Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00
CONTRIBUTING.md Update the Running Enso Section in Contribution Docs (#1250) 2020-11-05 21:08:30 +03:00
enso-philosophy.md Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00
getting-enso.md Bump GraalVM Version to 20.2.0 (#1094) 2020-08-28 13:03:09 +02:00
README.md [doc] Fix typo in docs/README.md (#1142) 2020-09-11 10:37:50 +01:00
SECURITY.md Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00

layout title category tags order
docs-index Enso Engine Developer Documentation summary
summary
readme
0

Enso Engine Developer Documentation

This folder contains the documentation for the implementation of the Enso programming language. The documentation is broken up by subject, within the below-listed categories, and each subject combines information about the design, specification, and implementation of the feature to which it pertains.

We provide a number of useful resources for getting a quick understanding of the Enso project:

  • The Enso Philosophy: Information on the design philosophy behind Enso, and why we build things in the way we do.
  • Contributing Guidelines: Information for people wanting to contribute to Enso (in many different ways).
  • Community Code of Conduct: The code of conduct for members of our community, developers and users alike.
  • Security Guidelines: Security guidelines for the Enso project, including supported versions and our vulnerability reporting process.
  • Getting Enso: Instructions for how to get and run a copy of Enso.

It is broken up into categories as follows:

  • Distribution: Information on how we distribute Enso to our users, and how Enso packages themselves work.
  • Language Server: Information on the Enso language server, its protocol, and how it integrates with the runtime.
  • Polyglot: Information on Enso's polyglot functionality, and how it is integrated into the surface Enso language.
  • RFCs: RFCs for Enso's development and evolution.
  • Runtime: Specification and documentation of the way that the Enso runtime is designed and implemented.
  • Semantics: A specification of Enso's semantics.
  • Style Guides: Style guides for the code written as part of the Enso project.
  • Syntax: A specification of Enso's syntax.
  • Types: A specification of Enso's type system and type theory.
  • Debugger: A specification of Enso's debugger.
  • Parser: Design and specification of the Enso parser.
  • Infrastructure: Description of the infrastructure for building Enso.