Annotate CallKind and DotCallKind in AST #195
Merged
Conversation
This file contains 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
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.
The information whether a
Callstands for a constructor, codefinition or toplevel definition is currently not recorded in the AST, but has to be reconstructed by looking up in the context what the name refers to. (Similarly forDotCallwhich can stand for destructors or codefinitions).This PR annotates the AST with
CallKindresp.DotCallKindand uses this information to display more accurate information on hover.Other small refactorings:
formattingandcodeactionsimplementations of the LSP server into their own modules.CtorandDtorin the evaluator toCallandDotCallin order to be consistent with the other AST representations.