[Sema] Check for already existential type while resolving existential #59015
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
xedin
approved these changes
May 23, 2022
hborla
reviewed
May 23, 2022
LucianoPAlmeida
force-pushed
the
existential-resolve
branch
from
e8a6c14 to
afae5c0
Compare
xedin
approved these changes
May 24, 2022
hborla
reviewed
May 24, 2022
LucianoPAlmeida
force-pushed
the
existential-resolve
branch
2 times, most recently
from
25029ed to
fd4d7c1
Compare
LucianoPAlmeida
force-pushed
the
existential-resolve
branch
from
fd4d7c1 to
20e02a2
Compare
|
@swift-ci Please smoke test |
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.
In those cases constraint type will be already resolved as
ExistentialTypewhich seems to make sense to just return it already.Fixes #58920