RequirementMachine: Concrete contraction needs to substitute the parent type of a subject type sometimes [5.7] #59325
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
…ral mode We resolve protocol typealiases to DependentMemberTypes because the Requirement Machine treats them as rewrite rules. However, it doesn't do this for typealiases in protocol extensions. Fixes rdar://problem/94150249.
…ects an invariant violation
…nt type of a subject type sometimes If you have generic parameters <T, U> and requirements of the form: - T : P - T == ConcreteType<U> - T.[P]U : SomeClass - T.[P]U : SomeProto And furthermore SomeClass does not conform to SomeProto, we can't leave `T.[P]U : SomeClass` unsubstituted; we still have to replace `T` with `ConcreteType<U>` to transform the latter two requirements into: - U : SomeClass - U : SomeProto "Concrete contraction" is easily the hackiest part of the Requirement Machine; I need to come up with a more principled solution for the problem that it solves sooner or later. Fixes rdar://problem/94150249.
|
@swift-ci Please test |
hborla
approved these changes
Jun 8, 2022
AnthonyLatsis
added
🍒 release cherry pick
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Cherry-pick of #59310.
If you have generic parameters
<T, U>and requirements of the form:T : PT == ConcreteType<U>T.[P]U : SomeClassT.[P]U : SomeProtoAnd furthermore SomeClass does not conform to SomeProto, we can't leave
T.[P]U : SomeClassunsubstituted; we still have to replaceTwithConcreteType<U>to transform the latter two requirements into:U : SomeClassU : SomeProto"Concrete contraction" is easily the hackiest part of the Requirement Machine; I need to come up with a more principled solution for the problem that it solves sooner or later.
Fixes rdar://problem/94150249.