Implement a Language Server for Technique #79
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Introduce a new top-level command technique language to run a server for the Language Server Protocol (LSP). This works by consuming JSON-RPC messages sent over stdin from an editor or IDE and then handling various methods being invoked. This implementation currently handles reporting compiler errors and re-formatting the document.
This gave us reason to extend the ranges shown in error messages to more accurately convey the location of the problematic code. Both the carets shown in textual errors in technique check and the red squiggle shown under erroneous code in an IDE benefit from this.
Finally, we've added
-as a valid filename, indicating that input to be checked or formatted is to be taken from standard input.