-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Add IgnoreContextualType fix on Keypath -> Function type mismatch. #31563
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
In If there's a way to provide enough context at the failure site so that the correct error message is emitted, I'd be curious to hear it. |
@swift-ci test |
Build failed |
b008d12
to
2f9891b
Compare
2f9891b
to
4b6165b
Compare
@swift-ci test |
4b6165b
to
e6901c5
Compare
e6901c5
to
3ac69a2
Compare
When simplifying a keypath constraint with a function type binding, single-parameter functions have the parameter type and the return type matched against the keypath root and value; whereas multiple-parameter functions cause an ambiguous failure (in `simplifyKeyPathConstraint`). Resolves rdar://problem/57930643
3ac69a2
to
7aed042
Compare
@swift-ci test |
Build failed |
…match. Cherry-pick swiftlang#31563, originally reviewed by @xedin. When simplifying a keypath constraint with a function type binding, single-parameter functions have the parameter type and the return type matched against the keypath root and value; whereas multiple-parameter functions cause an ambiguous failure (in `simplifyKeyPathConstraint`). Resolves rdar://problem/57930643
When simplifying a KeyPath constraint with a KeyPath type variable bound to a function type, single-parameter function types have the parameter type and the return type matched against the KeyPath root and value types; whereas multiple-parameter functions cause an ambiguous failure (in
simplifyKeyPathConstraint
).Resolves rdar://problem/57930643