mirror of
https://github.com/enso-org/enso.git
synced 2024-12-18 14:01:37 +03:00
96e50648dd
Modified UppercaseNames to now resolve methods without an explicit `here` to point to the current module. `here` was also often used instead of `self` which was allowed by the compiler. Therefore UppercaseNames pass is now GlobalNames and does some extra work - it translated method calls without an explicit target into proper applications. # Important Notes There was a long-standing bug in scopes usage when compiling standalone expressions. This resulted in AliasAnalysis generating incorrect graphs and manifested itself only in unit tests and when running `eval`, thus being a bit hard to locate. See `runExpression` for details. Additionally, method name resolution is now case-sensitive. Obsolete passes like UndefinedVariables and ModuleThisToHere were removed. All tests have been adapted. |
||
---|---|---|
.. | ||
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.