mirror of https://github.com/enso-org/enso.git synced 2024-12-25 17:32:28 +03:00

History

Jaroslav Tulach ab1ca54acd Profile the language server (#3389 ) In order to analyse why the `runner.jar` is slow to start, let's _"self sample"_ it using the [sampler library](https://bits.netbeans.org/dev/javadoc/org-netbeans-modules-sampler/org/netbeans/modules/sampler/Sampler.html). As soon as the `Main.main` is launched, the sampling starts and once the server is up, it writes its data into `/tmp/language-server.npss`. Open the `/tmp/language-server.npss` with [VisualVM](https://visualvm.github.io) - you should have one copy in your GraalVM `bin/jvisualvm` directory and there has to be a GraalVM to run Enso. #### Changelog - add: the `MethodsSampler` that gathers information in `.npss` format - add: `--profiling` flag that enables the sampler - add: language server processes the updates in batches	2022-05-10 12:44:05 +00:00
..
src	Profile the language server (#3389 )	2022-05-10 12:44:05 +00:00
README.md	Add a markdown style guide (#1022 )	2020-07-21 13:59:40 +01:00

Jaroslav Tulach ab1ca54acd

In order to analyse why the `runner.jar` is slow to start, let's _"self sample"_ it using the [sampler library](https://bits.netbeans.org/dev/javadoc/org-netbeans-modules-sampler/org/netbeans/modules/sampler/Sampler.html). As soon as the `Main.main` is launched, the sampling starts and once the server is up, it writes its data into `/tmp/language-server.npss`.

Open the `/tmp/language-server.npss` with [VisualVM](https://visualvm.github.io) - you should have one copy in your
GraalVM `bin/jvisualvm` directory and there has to be a GraalVM to run Enso.

#### Changelog

- add: the `MethodsSampler` that gathers information in `.npss` format
- add: `--profiling` flag that enables the sampler
- add: language server processes the updates in batches

2022-05-10 12:44:05 +00:00

src

Profile the language server (#3389 )

2022-05-10 12:44:05 +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.