Skip to content

[CSBindings] Account for literal bindings when checking "subtype of e… #37643

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
May 27, 2021

Conversation

xedin
Copy link
Contributor

@xedin xedin commented May 25, 2021

…xistential" property

It's important to know whether a binding set has all of its bindings
as subtypes of some existential type(s), type variables like that
should be delayed.

Incremental binding inference introduced a bug into computation of
this property by checking only directly inferable bindings, but
it's also important to check that there are no literal requirements
that can produce bindings, because that would mean that type variable
can never be just a subtype of existential type(s).

Resolves: rdar://77570994

@xedin xedin requested a review from hborla May 25, 2021 22:35
@xedin
Copy link
Contributor Author

xedin commented May 25, 2021

@swift-ci please test

@xedin
Copy link
Contributor Author

xedin commented May 25, 2021

@swift-ci please test source compatibility

@swift-ci
Copy link
Contributor

Build failed
Swift Test OS X Platform
Git Sha - 8f9f9e80c57f3ec943d2963ab7a3fadd0e067999

@xedin
Copy link
Contributor Author

xedin commented May 26, 2021

@swift-ci please test macOS platform

@xedin
Copy link
Contributor Author

xedin commented May 26, 2021

@swift-ci please test Windows platform

@xedin
Copy link
Contributor Author

xedin commented May 26, 2021

@swift-ci please test source compatibility

…xistential" property

It's important to know whether a binding set has all of its bindings
as subtypes of some existential type(s), type variables like that
should be delayed.

Incremental binding inference introduced a bug into computation of
this property by checking only directly inferable bindings, but
it's also important to check that there are no literal requirements
that can produce bindings, because that would mean that type variable
can never be just a subtype of existential type(s).

Resolves: rdar://77570994
@xedin
Copy link
Contributor Author

xedin commented May 26, 2021

@swift-ci please test

@swift-ci
Copy link
Contributor

Build failed
Swift Test OS X Platform
Git Sha - cf13e29

@xedin
Copy link
Contributor Author

xedin commented May 26, 2021

@swift-ci please test macOS platform

@swift-ci
Copy link
Contributor

Build failed
Swift Test OS X Platform
Git Sha - cf13e29

@xedin
Copy link
Contributor Author

xedin commented May 27, 2021

@shahmishal macOS builds are timing out on macOS-53 - 19:46:06 Build timed out (after 83 minutes). Marking the build as failed.

@xedin
Copy link
Contributor Author

xedin commented May 27, 2021

@swift-ci please test macOS platform

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.

3 participants