mirror of
https://github.com/enso-org/enso.git
synced 2024-12-24 19:03:27 +03:00
dc30e44b60
New plan to [fix the `sbt` build](https://www.pivotaltracker.com/n/projects/2539304/stories/182209126) and its annoying: ``` log.error( "Truffle Instrumentation is not up to date, " + "which will lead to runtime errors\n" + "Fixes have been applied to ensure consistent Instrumentation state, " + "but compilation has to be triggered again.\n" + "Please re-run the previous command.\n" + "(If this for some reason fails, " + s"please do a clean build of the $projectName project)" ) ``` When it is hard to fix `sbt` incremental compilation, let's restructure our project sources so that each `@TruffleInstrument` and `@TruffleLanguage` registration is in individual compilation unit. Each such unit is either going to be compiled or not going to be compiled as a batch - that will eliminate the `sbt` incremental compilation issues without addressing them in `sbt` itself. fa2cf6a33ec4a5b2e3370e1b22c2b5f712286a75 is the first step - it introduces `IdExecutionService` and moves all the `IdExecutionInstrument` API up to that interface. The rest of the `runtime` project then depends only on `IdExecutionService`. Such refactoring allows us to move the `IdExecutionInstrument` out of `runtime` project into independent compilation unit. |
||
|---|---|---|
| .. | ||
| builtin-base-methods.md | ||
| caching.md | ||
| demand-analysis.md | ||
| execution-server-flow.md | ||
| function-call-flow.md | ||
| instruments.md | ||
| ir-caching.md | ||
| README.md | ||
| runtime-features.md | ||
| searcher.md | ||
| unbounded-recursion.md | ||
| layout | title | category | tags | order | ||
|---|---|---|---|---|---|---|
| section-summary | Enso Runtime | runtime |
|
0 |
Enso Runtime
The Enso runtime refers to both the compiler and the optimising JIT runtime for Enso. While this might seem like a strange choice, it makes sense internally as the components are integrated to a level not seen in most languages. 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.
This folder contains all of the documentation related to the runtime, which is broken up as follows:
- Caching: A description of the runtime's value caching mechanism.
- Demand Analysis: A specification for the demand analysis process in the Enso compiler that assists users with working with suspended computations.
- Function Calling Flow: A description of the involved logic that goes into a calling a function performantly in the Enso runtime, while also supporting the flexible function syntax.
- Runtime Features: A description of (and plan for) the features of the Enso runtime.
- Unbounded Recursion: An exploration of techniques for achieving unbounded recursion on the JVM.
- Instruments: A description of instrumentation in the language runtime.
- Execution Server Flow: An explanation of how the execution server orchestrates Enso's execution.
- Builtin Base Methods: An explanation of the DSL we use for defining builtin types and methods.
- Searcher: An explanation of how the searcher works.
- Instruments: An explanation of how we compile Truffle instrumentation.
- IR Caching: An explanation of how we cache the compiler IR to reduce startup times.