[Protocol checker] Eliminate ordering dependency with "unsatisfied" check #34670
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
…heck. When checking whether an @objc protocol requirement is considered satisfied by another requirement with the same selector, make sure to use "getWitness" (rather than "hasWitness") to avoid order dependencies in the computation. These are fantastically hard to reproduce in small test cases.
Member
Author
|
@swift-ci please smoke test |
Member
Author
|
@swift-ci please test source compatibility |
Member
Author
Member
Author
Member
Author
|
@swift-ci please test source compatibility |
Member
Author
|
@swift-ci please smoke test Linux |
Member
Author
|
@swift-ci please test source compatibility |
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.
When checking whether an
@objcprotocol requirement is consideredsatisfied by another requirement with the same selector, make sure
to use "getWitness" (rather than "hasWitness") to avoid order
dependencies in the computation. These are fantastically hard
to reproduce in small test cases.