enso/engine
Hubert Plociniczak 059bb8c7e9
Apply automatic formatting prior to turning on checks (#3405)
Result of automatic formatting with `scalafmtAll` and `javafmtAll`.
Prerequisite for https://github.com/enso-org/enso/pull/3394

### Important Notes

This touches a lot of files and might conflict with existing PRs that are in progress. If that's the case, just run
`scalafmtAll` and `javafmtAll` after merge and everything should be in order since formatters should be deterministic.
2022-04-19 12:34:34 +02:00
..
language-server Apply automatic formatting prior to turning on checks (#3405) 2022-04-19 12:34:34 +02: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 Apply automatic formatting prior to turning on checks (#3405) 2022-04-19 12:34:34 +02:00
runner Implement the component resolving algorithm (#3244) 2022-02-03 10:40:39 +03:00
runtime Apply automatic formatting prior to turning on checks (#3405) 2022-04-19 12:34:34 +02: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.