-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[5.3][ConstraintSystem] Detect and diagnose inability to infer type of clo… #31810
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 |
Build failed |
Build failed |
@swift-ci please test |
Build failed |
Build failed |
@swift-ci please test |
Build failed |
Build failed |
…sure parameter(s) Detect situation when it's impossible to determine types for closure parameters used in the body from the context. E.g. when a call closure is associated with refers to a missing member. ```swift struct S { } S.foo { a, b in } // `S` doesn't have static member `foo` let _ = { v in } // not enough context to infer type of `v` _ = .foo { v in } // base type for `.foo` couldn't be determined ``` Resolves: [SR-12815](https://bugs.swift.org/browse/SR-12815) Resolves: rdar://problem/63230293
@swift-ci please test |
Build failed |
Build failed |
…sure parameter(s)
Cherry-pick of #31809
Detect situation when it's impossible to determine types for
closure parameters used in the body from the context. E.g.
when a call closure is associated with refers to a missing
member.
Scope: Diagnostics related to parameters of a closure
Resolves: rdar://problem/63230293
Risk: Low
Testing: Added a regression tests
Reviewer: @hborla
Resolves: SR-12815
Resolves: rdar://problem/63230293