Skip to content

[CSBindings] Refactor a check to produce follow-up direct supertype b… #30436

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
Mar 16, 2020

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Mar 16, 2020

…indings

This is a follow-up to #30113
which cased a regression because it was placed under a check which
allows direct supertypes to be inferred if previous (failing) binding
has a supertype as well which has nothing to do with collection
inference.

Let's combine supertype check and inference logic to avoid such
confusion in the future.

Resolves: rdar://problem/60501780

…indings

This is a follow-up to swiftlang#30113
which cased a regression because it was placed under a check which
allows direct supertypes to be inferred if previous (failing) binding
has a supertype as well which has nothing to do with collection
inference.

Let's combine supertype check and inference logic to avoid such
confusion in the future.

Resolves: rdar://problem/60501780
@xedin xedin requested a review from DougGregor March 16, 2020 19:22
@xedin
Copy link
Contributor Author

xedin commented Mar 16, 2020

@swift-ci please smoke test

@xedin
Copy link
Contributor Author

xedin commented Mar 16, 2020

@swift-ci please test source compatibility

@xedin xedin merged commit 01073be into swiftlang:master Mar 16, 2020
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