-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support MatchType for SemanticDB #14608
Merged
Merged
Changes from 1 commit
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
7817912
Add generated semanticdb source code
tanishiking 0480dec
Support MatchType in semanticdb
tanishiking fa4cb01
Remove LambdaType
tanishiking 28d59a0
Assign types to type variables in match case types
tanishiking 2ca6fb2
Remove `case` property from the symbol of type variable
tanishiking 4fa62e2
Don't craft the NamedType symbol
tanishiking 2693983
Merge branches for TypeRef/TermRef with Symbol and Name
tanishiking 18b8901
Add undefined type case for TypeRef with no symbols
tanishiking b070667
Retrieve a symbol for typeref to refinements in RefinedType
tanishiking 60c336e
Resolve symbols in refinements by fake symbols
tanishiking be31d56
Resolve symbol occurrences of select type fields
tanishiking 9375ab1
Resolve real symbol from nested refined type
tanishiking 50a43b9
No need to resolve fake symbols from RefinedTypes
tanishiking 8465366
Dealias type for looking up symbols in refinements
tanishiking ba24fe1
Add test file for semanticdb and ignore symbol lookup failures
tanishiking File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you have an idea why
.A
and.a
do not have occurrences here?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess this is because
.A
and.a
(access the field of refinements), don't have symbols (we're crafting fake symbols for them), andExtractSemanticDB
doesn't resolve the fake symbols by name.We can see the same problem around here:
https://github.com/lampepfl/dotty/blob/60c336ef34fe0e77851a7652b910db13b84dfe6f/tests/semanticdb/expect/Advanced.expect.scala#L17
I'll take a look 👀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess looking again
registerUse
orregisterUseGuarded
still only assume real symbols, for exampleSelect
tree checks that the symbol exists, without checking for a registered fake symbol - this could be a follow up PRThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As per
foo.A
, b964694 as you mentioned, you're right, we could fix the issue by looking up the fake symbols andregisterUse
them.In terms of
foo.a
(field access to structural type), it is transformed tofoo.selectDynamic("a")
by Typer here ↓https://github.com/lampepfl/dotty/blob/b9646942facccdcc110753f019c14b941fae870d/compiler/src/dotty/tools/dotc/typer/Dynamic.scala#L49-L65
We have to check if
qual
is something likeApply(Select(Ident(foo), name), List(Literal(Constant("a")))) if name == nme.applyDynamic || name == nme.selectDynamic || name == nme.updateDynamic || name == nme.applyDynamicNamed
, and lookup symbol fora
fromfoo
(This is not yet fixed, can I work on this in another PR?)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is fine for another PR