mirror of https://github.com/enso-org/enso.git synced 2024-12-24 19:03:27 +03:00

History

Dmitry Bushev 98d30bccf3 Enable caching in visualization functions (#3618 ) 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" } } ```	2022-08-10 12:01:33 +00:00
..
src	Enable caching in visualization functions (#3618 )	2022-08-10 12:01:33 +00:00
README.md	Add a markdown style guide (#1022 )	2020-07-21 13:59:40 +01:00

Enable caching in visualization functions (#3618 )

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"
}
}
```

2022-08-10 12:01:33 +00:00

src

Enable caching in visualization functions (#3618 )

2022-08-10 12:01:33 +00:00

README.md

Add a markdown style guide (#1022 )

2020-07-21 13:59:40 +01:00

README.md

Enso Language Server

The Enso Language Server is responsibile for providing a remote-communication protocol for the runtime, exposing many of its features to the users. In addition it provides the backing service for much of the IDE functionality associated with the language. It encompasses the following functionality:

Introspection Services: Giving clients the ability to observe information about their running code including values, types, profiling information, and debugging.
Code Execution: The ability for clients to execute arbitrary Enso code in arbitrary scopes. This can be used in conjunction with the above to provide a REPL with an integrated debugger.
Code Completion: Sophisticated completion functionality that refines suggestions intelligently based on context.
Node Management: Tracking and providing the language server's internal node representation of the Enso program.
Code Analysis: Analysis functionality for Enso code (e.g. find usages, jump-to-definition, and so on).
Refactoring: Refactoring functionality for Enso code (e.g. rename, move, extract, and so on).
Type Interactions: Features for type-driven-development that allow users to interact with the types of their programs.