-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[CodeCompletion] Unresolved member completion at type parameter position #21249
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
Merged
Merged
Changes from all commits
Commits
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 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
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
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.
I don't understand what effect this change has.
getTypeOfMember
in code-completion seems to do a bunch of things that the one onTypeBase
doesn't, includingeraseArchetypes
, and they also use different substitution flags. We currently are trying hard to avoid having archetypes leak into results where they show up badly when printed, per the comment oneraseArchetypes
.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.
Are the changes below to
mapTypeIntoContext
supposed to rectify this? If so, how does that compare toeraseArchetypes
?Uh oh!
There was an error while loading. Please reload this page.
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.
We want to keep
ArchetypeType
here becauseT
might be anArchetypeType
and we want to check if result ofdeclTy
is convertible toT
.Let's say
T
is archetypeU
which conforms toHasStatic
protocol andVD
isstatic var instance: Self { get }
,getTypeOfMember(VD, T)
returnsHasStatic
protocol, but that is not convertible to archetypeU
. ButT->getTypeOfMember(CurrModule, VD)
correctly returnsU
.This is just a filtering logic that checks
VD
can be referenced by "implicit member expression" syntax inT
type context. The result ofdeclTy
isn't used anywhere else. The type name for completion result is re-constructed by result builder.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.
Okay, thanks for explaining!