enso/engine
Radosław Waśko 20be5516a5
Aggregates in the Database library - MVP (#3353)
Implements infrastructure for new aggregations in the Database. It comes with only some basic aggregations and limited error-handling. More aggregations and problem handling will be added in subsequent PRs.

# Important Notes
This introduces basic aggregations using our existing codegen and sets-up our testing infrastructure to be able to use the same aggregate tests as in-memory backend for the database backends.

Many aggregations are not yet implemented - they will be added in subsequent tasks.

There are some TODOs left - they will be addressed in the next tasks.
2022-03-28 15:51:37 +00:00
..
language-server Implement Documentation Sections API (#3360) 2022-03-25 10:49:37 +03: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 Implement Documentation Sections API (#3360) 2022-03-25 10:49:37 +03:00
runner Implement the component resolving algorithm (#3244) 2022-02-03 10:40:39 +03:00
runtime Aggregates in the Database library - MVP (#3353) 2022-03-28 15:51:37 +00: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.