🍒 [5.7] AST: Fix bug in subclass composition minimization #58604
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
Now that opened archetype signatures are generalized to encompass outer generic contexts, the number of requirements in the generic signature is not always indicative of whether the minimal type is also a composition.
Trust the `GenericSignature` class with upholding its invariants and assert that a superclass bound is in the right place instead of prepending it.
Contributor
|
@swift-ci Please test |
DougGregor
approved these changes
May 2, 2022
AnthonyLatsis
added
🍒 release cherry pick
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
ProtocolComposition::build. When opened archetype signatures were upgraded to encompass surrounding generic contexts, the fast path ceased to serve this purpose in the presence of requirements on other generic parameters.