mirror of https://github.com/enso-org/enso.git synced 2024-11-22 22:10:15 +03:00

History

Hubert Plociniczak 21dc90a0ed OpenFileCmd sends a reply when finished (#8225 ) * OpenFileCmd sends a reply when finished Lack of reply and therefore a non-determinism on when OpenFile handler can finish, led to some sporadic instability. Once caches format got changed, things were taking such a long time that I wasn't able to start even a basic project (requests would start to timeout). The change also removes PushContextCmd from synchronous cmds (as introduced in #798 to remove initialization problems in tests as well as in real scenarions); the change did the job but was also a bit controversial. The change can also help with randomly failing applies (#8174) as IDE kept closing and opening the project that might have exploited the race-condition. * Adapt tests * Make tests more resilient to out of order messages * Drop retries that lead to confusing errors * less random failures * s/OpenFileNotification/OpenFileRequest	2023-11-07 23:59:42 +01:00
..
src	OpenFileCmd sends a reply when finished (#8225 )	2023-11-07 23:59:42 +01:00
README.md	Add a markdown style guide (#1022 )	2020-07-21 13:59:40 +01:00

Hubert Plociniczak 21dc90a0ed

OpenFileCmd sends a reply when finished (#8225 )

* OpenFileCmd sends a reply when finished

Lack of reply and therefore a non-determinism on when OpenFile handler
can finish, led to some sporadic instability. Once caches format got
changed, things were taking such a long time that I wasn't able to start
even a basic project (requests would start to timeout).
The change also removes PushContextCmd from synchronous cmds (as
introduced in #798 to remove initialization problems in tests as well as
in real scenarions); the change did the job but was also a bit
controversial.
The change can also help with randomly failing applies (#8174) as IDE kept
closing and opening the project that might have exploited the
race-condition.

* Adapt tests

* Make tests more resilient to out of order messages

* Drop retries that lead to confusing errors

* less random failures

* s/OpenFileNotification/OpenFileRequest

2023-11-07 23:59:42 +01:00

src

OpenFileCmd sends a reply when finished (#8225 )

2023-11-07 23:59:42 +01: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.