mirror of
https://github.com/enso-org/enso.git
synced 2024-11-24 00:27:16 +03:00
98d30bccf3
PR allows to attach metod pointers as a visualization expressions. This way it allows to attach a runtime instrument that enables caching of intermediate expressions.
# Important Notes
ℹ️ API is backward compatible.
To attach the visualization with caching support, the same `executionContext/attachVisualisation` method is used, but `VisualisationConfig` message should contain the message pointer.
While `VisualisationConfiguration` message has changed, the language server accepts both new and old formats to keep visualisations working in IDE.
#### Old format
```json
{
"executionContextId": "UUID",
"visualisationModule": "local.Unnamed.Main",
"expression": "x -> x.to_text"
}
```
#### New format
```json
{
"executionContextId": "UUID",
"expression": {
"module": "local.Unnamed.Main",
"definedOnType": "local.Unnamed.Main",
"name": "encode"
}
}
```
|
||
|---|---|---|
| .. | ||
| language-server | ||
| launcher/src | ||
| polyglot-api/src | ||
| runner | ||
| runtime | ||
| runtime-instrument-id-execution/src/main/java/org/enso/interpreter/instrument | ||
| runtime-instrument-repl-debugger/src/main/java/org/enso/interpreter/instrument | ||
| runtime-instrument-runtime-server/src/main/java/org/enso/interpreter/instrument | ||
| runtime-language-epb/src/main/java/org/enso/interpreter/epb | ||
| runtime-with-instruments/src/test | ||
| README.md | ||
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.