[5.9][CSSimplify] Add special handling if specialized type comes from TypeExpr
#66885
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
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 #66796
Add a special case for
TypeExprdue to i.e. context specialization,in such cases there is nothing for the solver to "open" so we need to
form opened type map manually.
Scope: Attempts to specialize type references (including in specialized extensions).
Main Branch PR: [CSSimplify] Add special handling if specialized type comes from
TypeExpr#66796Risk: Low
Resolves: rdar://111059036
Reviewed By: @DougGregor
Testing: Added regression test-cases to the suite.
Resolves: rdar://111059036
(cherry picked from commit e1e933c)
(cherry picked from commit 5e30445)