-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[CSRanking] Favour concrete members over protocol requirements in Swift 5 mode #18951
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
rudkx
merged 6 commits into
swiftlang:master
from
hamishknight:concrete-is-better-swift5
Aug 30, 2018
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
1520dbb
[test] Expand AnyObject ambiguity test to cover methods and subscripts
hamishknight 286f164
[CSRanking] Favour members on concrete types over protocol members
hamishknight 1912d28
[CSRanking] Exclude concrete-over-protocol rule from dynamic lookup r…
hamishknight 37a9490
[Revert Me] Disable language version check temporarily
hamishknight b72d7e2
Merge remote-tracking branch 'upstream/master' into concrete-is-bette…
hamishknight bee01ed
Revert "[Revert Me] Disable language version check temporarily"
hamishknight 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
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
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.
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.
I just ran into an issue with this change.
If you compare two declarations in two different protocols, e.g.:
it always returns
proto2
.For the concrete vs. protocol case it doesn't seem (from a quick look at the code) to be doing the right thing either.
[EDIT: I meant to make one protocol refine the other; my expectation is that we would return
Q's f()
as being more specialized.]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.
Ah, I see – not sure how I missed that! We should really be doing an is-a check rather than comparing pointers, i.e:
I can't immediately think of a test case that trips up the current logic though – for the case you mention of having a protocol refine another, we should be filtering out overridden protocols requirements in name lookup.
Do you have a test case that trips up the current logic? Would be nice to have one for the fix.
Could you please elaborate on this? I can't immediately think of a concrete vs. protocol case where it does the wrong thing.
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'm experimenting with changes that call
compareDeclarations
on arbitrary overloads in a disjunction to see if they are ordered. I don't have a test case that I know will hit this otherwise.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.
Ah okay, sorry about that! I've submitted a fix: #19561