enso/engine
Radosław Waśko 891f064a6a
Extend Aggregate_Spec test suite with tests for missed edge-cases to ensure the feature is well-tested on all backends (#3383)
Implements https://www.pivotaltracker.com/story/show/181805693 and finishes the basic set of features of the Aggregate component.

Still not all aggregations are supported everywhere, because for example SQLite has quite limited support for aggregations. Currently the workaround is to bring the table into memory (if possible) and perform the computation locally. Later on, we may add more complex generator features to emulate the missing aggregations with complex sub-queries.
2022-04-12 11:02:01 +00:00
..
language-server Fix multiline code docparser (#3379) 2022-04-06 04:39:58 +00: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 Fix docparser (#3370) 2022-03-31 04:44:34 +00:00
runner Implement the component resolving algorithm (#3244) 2022-02-03 10:40:39 +03:00
runtime Extend Aggregate_Spec test suite with tests for missed edge-cases to ensure the feature is well-tested on all backends (#3383) 2022-04-12 11:02:01 +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.