-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[ConstraintSystem] Type of key path expression should be a known KeyPath
type
#24234
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
Conversation
@swift-ci please test |
@swift-ci please test source compatibility |
Build failed |
Build failed |
@swift-ci please test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks
Build failed |
…Path` type Currently `getPotentialBindingsForRelationalConstraint` doesn't respect the fact that type of key path expression has to be a form of `KeyPath`, instead it could eagerly try to bind it to `Any` or other contextual type if it's only available information. This patch aims to fix this situation by filtering potential bindings available for type variable representing type of the key path expression. Resolves: SR-10467
@swift-ci please test |
Build failed |
@swift-ci please test source compatibility |
Build failed |
Currently
getPotentialBindingsForRelationalConstraint
doesn'trespect the fact that type of key path expression has to be a
form of
KeyPath
, instead it could eagerly try to bind it toAny
or other contextual type if it's only availableinformation.
This patch aims to fix this situation by filtering potential
bindings available for type variable representing type of
the key path expression.
Resolves SR-10467.