RequirementMachine: Concrete contraction needs to substitute the parent type of a subject type sometimes #59310
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.
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 replaceT
withConcreteType<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.