Skip to content

[GSB] Use resolved type when looking for a representative constraint. #18265

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
Jul 26, 2018

Conversation

DougGregor
Copy link
Member

When looking for a representative superclass constraint, take into
account other same-type constraints by comparing against the resolved
superclass constraint type rather than the type as spelled.

Fixes SR-8179 / rdar://problem/41851224.

@DougGregor DougGregor force-pushed the gsb-resolved-superclass-type branch from 431f44e to 3f5f50f Compare July 26, 2018 19:41
When looking for a representative superclass constraint, take into
account other same-type constraints by comparing against the resolved
superclass constraint type rather than the type as spelled.

Fixes SR-8179 / rdar://problem/41851224.
@DougGregor DougGregor force-pushed the gsb-resolved-superclass-type branch from 3f5f50f to b421d08 Compare July 26, 2018 19:42
@DougGregor
Copy link
Member Author

@swift-ci please smoke test and merge

@swift-ci swift-ci merged commit c643d1d into swiftlang:master Jul 26, 2018
@DougGregor DougGregor deleted the gsb-resolved-superclass-type branch July 26, 2018 20:26
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