enso/engine
Hubert Plociniczak 66e2135b0d
Initialize AtomConstructor's fields via local vars (#3330)
The mechanism follows a similar approach to what is being in functions
with default arguments.
Additionally since InstantiateAtomNode wasn't a subtype of EnsoRootNode it
couldn't be used in the application, which was the primary reason for
issue #181449213.
Alternatively InstantiateAtomNode could have been enhanced to extend
EnsoRootNode rather than RootNode to carry scope info but the former
seemed simpler.

See test cases for previously crashing and invalid cases.
2022-03-21 09:15:14 +00:00
..
language-server Fix Error Payload Serialization (#3315) 2022-03-04 11:57:49 +03:00
launcher/src Data analysts should be able to use Text.location_of to find indexes within string using various matchers (#3324) 2022-03-12 19:42:00 +00:00
polyglot-api/src Fix teardown for engine's testcases (#3303) 2022-03-03 15:36:01 +01:00
runner Implement the component resolving algorithm (#3244) 2022-02-03 10:40:39 +03:00
runtime Initialize AtomConstructor's fields via local vars (#3330) 2022-03-21 09:15:14 +00:00
README.md Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00

The Enso Engine

The Enso engine is the codebase responsible for compiling and executing Enso code, as well as providing language server functionality to users of the language. It is subdivided into two major components:

  • Language Server: The Enso language service.
  • Polyglot API: The truffle-boundary safe API for communication between the language server and the runtime.
  • Runner: The command-line interface for Enso.
  • Runtime: The compiler and interpreter for Enso.