Skip to content

[5.0][ConstraintSystem] Bind Self to correct contextual type for nested ty… #14160

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 25, 2018

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Jan 25, 2018

…pes in protocol

If something that we are trying to contextually bind is a nested type inside
protocol or protocol extension, let's try to find the innermost conforming type
from the current declaration context and map Self parameter of the protocol
to that nominal type. Since nested types in protocols aren't yet implemented this
is going to result in failure, but that's better than crashing.

Resolves: rdar://problem/36449760
(cherry picked from commit a11263b)

…pes in protocol

If something that we are trying to contextually bind is a nested type inside
protocol or protocol extension, let's try to find the innermost conforming type
from the current declaration context and map Self parameter of the protocol
to that nominal type. Since nested types in protocols aren't yet implemented this
is going to result in failure, but that's better than crashing.

Resolves: rdar://problem/36449760
(cherry picked from commit a11263b)
@xedin
Copy link
Contributor Author

xedin commented Jan 25, 2018

@swift-ci please smoke test and merge

@xedin xedin changed the title [ConstraintSystem] Bind Self to correct contextual type for nested ty… [5.0][ConstraintSystem] Bind Self to correct contextual type for nested ty… Jan 25, 2018
@swift-ci swift-ci merged commit 9cd9f26 into swiftlang:swift-5.0-branch Jan 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants