-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[ConstraintSystem] Handle ambiguities caused by requirement failures #63222
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
[ConstraintSystem] Handle ambiguities caused by requirement failures #63222
Conversation
@LucianoPAlmeida it might indeed fix that, I add a test-case. |
Awesome! |
@LucianoPAlmeida Case from this comment is indeed improved by these changes, the rest are diagnosed property as well. |
da8555e
to
57a29c7
Compare
@swift-ci please test |
@swift-ci please test Linux platform |
1 similar comment
@swift-ci please test Linux platform |
The logic is common for all types of fixes that represent a requirement failure.
Aggregate all requirement failures (regardless of kind) that belong to the same locator and diagnose them as an ambiguity (if there is more than one overload) or as the singular failure if all solutions point to the same overload.
@swift-ci please clean test Linux platform |
57a29c7
to
09cab70
Compare
@swift-ci please test |
…ed result builder methods Only way to aggregate build* methods is via source locations because each result builder kind would create a new build* expression node.
09cab70
to
e99f0e2
Compare
@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.
Nice!
@swift-ci please smoke test macOS platform |
2 similar comments
@swift-ci please smoke test macOS platform |
@swift-ci please smoke test macOS platform |
@swift-ci please test macOS platform |
1 similar comment
@swift-ci please test macOS platform |
Please test with following PRs: @swift-ci please smoke test macOS platform |
Please test with following PRs: @swift-ci please smoke test macOS platform |
@swift-ci please smoke test macOS platform |
full suite is failing with unrelated failures:
|
Aggregate all requirement failures (regardless of kind) that belong
to the same locator and diagnose them as an ambiguity (if there is
more than one overload) or as the singular failure if all solutions
point to the same overload.
Resolves: #56173
Resolves: rdar://79357256
Resolves: rdar://104135510