mirror of
https://github.com/enso-org/enso.git
synced 2024-12-25 03:43:41 +03:00
7abc281bd8
When the `project.yaml` specifies an unknown edition, the project is started with the fallback edition (current engine version). It works this way: - IDE sends project/open request to project manager (specifying only which project to open) - project manager resolves the project edition (based on `project.yaml`) or selects the fallback if the requested edition cannot be loaded - project manager starts the language server specifying the edition with the `--server-edition` command line parameter - language server specifies the correct edition when creates the runtime context |
||
---|---|---|
.. | ||
language-server | ||
launcher/src | ||
polyglot-api/src | ||
runner | ||
runtime | ||
runtime-instrument-id-execution/src/main/java/org/enso/interpreter/instrument | ||
runtime-instrument-repl-debugger/src/main/java/org/enso/interpreter/instrument | ||
runtime-instrument-runtime-server/src/main/java/org/enso/interpreter/instrument | ||
runtime-language-epb/src/main/java/org/enso/interpreter/epb | ||
runtime-with-instruments/src/test | ||
runtime-with-polyglot/src/test | ||
README.md |
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.