21dc90a0ed
* OpenFileCmd sends a reply when finished Lack of reply and therefore a non-determinism on when OpenFile handler can finish, led to some sporadic instability. Once caches format got changed, things were taking such a long time that I wasn't able to start even a basic project (requests would start to timeout). The change also removes PushContextCmd from synchronous cmds (as introduced in #798 to remove initialization problems in tests as well as in real scenarions); the change did the job but was also a bit controversial. The change can also help with randomly failing applies (#8174) as IDE kept closing and opening the project that might have exploited the race-condition. * Adapt tests * Make tests more resilient to out of order messages * Drop retries that lead to confusing errors * less random failures * s/OpenFileNotification/OpenFileRequest |
||
|---|---|---|
| .. | ||
| src | ||
| README.md | ||
Enso Runtime
The Enso runtime is responsible for the actual execution of Enso code. This means that it encompasses the following functionality:
- Parsing: Taking Enso code as input and generating an AST that maintains a sophisticated set of information about the input.
- Desugaring: Reducing the user-facing Enso code into a simplified language
known as
Core. - Type Inference: Inferring the types of bindings in the user's code.
- Type Checking: Checking that the inferred and provided types for bindings match up across the codebase.
- Optimisation: Static optimisation processes to improve the performance of the user's program.
- Code Execution: Actually running the Enso code.
- Introspection Hooks: Providing hooks into the running code to allow the language server to inspect information about the code as it runs.
Truffle Nodes creation convention
All Truffle nodes that are expected to be created as part of ASTs should
implement a public, static build method for creating an instance. If the node
is DSL generated, the build method should delegate to the autogenerated
create method, so that nodes are always created with build. Such a
convention allows us to easily switch node back and forth between manual and DSL
generated implementations, without the need to change its clients.
The only exception are nodes that are never expected to be a part of an AST –
e.g. root nodes of builtin functions, for which an asFunction method should be
implemented instead.
This convention should be implemented for every node throughout this codebase – if you see one not obeying it – please fix it.