add optional async extension for lsp clients #424
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The new crate lsp_client holds functions that can be used to apply the features from ng_async. This way the json parsing is performed in a rust thread. There's currently only support for lsp-mode.
|
Is this still necessary given the upstream JSON parser? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is still very unstable. It seems to depend on the lsp server, the size of a project and the lsp requests. I'll take a deeper look and try to fix it. But I think it makes sense to merge it, so others can also take a look.
The changes depend on emacs-lsp/lsp-mode#2978