mirror of
https://github.com/enso-org/enso.git
synced 2024-11-24 00:27:16 +03:00
c87d1d6767
By default all polyglot symbols that have been imported were always exported. This means that importing a module that had some polyglot imports brought them into the scope automatically. This didn't follow our desired semantics. Fixes task 3 in https://www.pivotaltracker.com/story/show/183833055. |
||
|---|---|---|
| .. | ||
| 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 | ||
| 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.