mirror of
https://github.com/enso-org/enso.git
synced 2024-11-24 00:27:16 +03:00
1eec315ce1
`main` method is now special because it is trully static i.e. no implicit `self` is being generated for it. But since REPL's `main` isn't called `main` its invocation was missing an argument. Follow up on https://github.com/enso-org/enso/pull/3569 # Important Notes Will work on adding a CI test for REPL to avoid problems with REPL in a follow up PR. |
||
---|---|---|
.. | ||
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.