mirror of
https://github.com/enso-org/enso.git
synced 2024-12-23 18:15:21 +03:00
56cc9561b1
close #8431 Fixes the scenario: - user sends `executionContext/executeExpression` - program execution is scheduled - during the compilation the already compiled `IR` is loaded from the cache (reading invalid alias analysis graph) - during the codegen the local scope with that aliasing graph is propagated to the runtime - `EvalNode` compiles the expression to execute with the local scope containing an invalid aliasing graph - compilation fails in the `AliasAnalysis` pass because of the clashing IDs in the graph |
||
---|---|---|
.. | ||
interpreter-dsl-test/src/test/java/org/enso/interpreter/dsl/test | ||
language-server | ||
launcher/src | ||
polyglot-api/src | ||
runner | ||
runtime | ||
runtime-compiler/src/main | ||
runtime-instrument-common/src | ||
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 | ||
runtime-parser/src | ||
runtime-with-instruments/src | ||
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.