enso/docs
Dmitry Bushev f0115587b0
Handle PanicSentinel in Interpreter (#1436)
PR adds the ability to handle runtime exceptions 
in the interpreter and continue the execution 
passing the PanicSentinel value.
2021-02-02 12:02:00 +03:00
..
debugger Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00
distribution Better component handling in the project manager (#1399) 2021-01-15 15:26:51 +00:00
infrastructure Fix the project manager reflection configuration (#1394) 2021-01-14 10:46:01 +00:00
language-server Handle PanicSentinel in Interpreter (#1436) 2021-02-02 12:02:00 +03:00
parser Preparation for more parser work (#1363) 2020-12-18 14:25:30 +00:00
polyglot Fluent Java Interop & Method Dispatch Refactor (#1443) 2021-02-01 15:56:20 +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 Update README.md (#1442) 2021-02-01 11:01:07 +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 Project Manager Native Image (#1318) 2020-12-09 14:58:11 +01:00
enso-philosophy.md Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00
getting-enso.md Bump the development version number (#1389) 2021-01-06 08:57:02 +00: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.