enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-12-18 07:42:21 +03:00
Code Issues Projects Releases Wiki Activity
3e74afca51
enso/docs/runtime
History
Hubert Plociniczak a04425576a
Force recompilation if imported module has changed (#3703) 
IR cache never really took into account a situation when a binding from the imported module has changed. In other words, it would continue to happily use the serialized metadata without noticing that it changed.

This change forces cache invalidation when any of the imported modules was invalidated (or rather not loaded from cache).

# Important Notes
Added simple test infrastructure that simulates file modifications that would trigger the initial cache invalidation.
If they succeed, cache invalidation is propagated thus causing an error.
2022-09-15 13:41:58 +00:00
..
builtin-base-methods.md Opt-in TCO (#1219) 2020-10-15 16:52:26 +02:00
caching.md Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00
demand-analysis.md Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00
execution-server-flow.md Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00
function-call-flow.md Opt-in TCO (#1219) 2020-10-15 16:52:26 +02:00
instruments.md Register instruments/language in their own compilation units to fix the sbt build issues (#3509) 2022-06-13 14:09:08 +00:00
ir-caching.md Force recompilation if imported module has changed (#3703) 2022-09-15 13:41:58 +00:00
README.md Design the support for IR serialization (#1868) 2021-07-15 13:14:32 +01:00
runtime-features.md Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00
searcher.md Add HTML Documentation API (#1758) 2021-06-01 15:43:22 +03:00
unbounded-recursion.md Add a markdown style guide (#1022) 2020-07-21 13:59:40 +01:00

README.md

layout title category tags order
section-summary Enso Runtime runtime
runtime
readme
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.