Skip to content

[Diagnostics] Diagnose general ambiguity failures in diagnoseAmbiguityWithFixes #29056

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
Jan 8, 2020

Conversation

hborla
Copy link
Member

@hborla hborla commented Jan 7, 2020

For now, we only emit the general error message no exact matches in call to x with a note pointing to each candidate. If we don't have the candidate's source location, we emit a note at the call site with the candidate's type.

@hborla hborla requested a review from xedin January 7, 2020 23:34
@hborla
Copy link
Member Author

hborla commented Jan 7, 2020

@swift-ci please smoke test

@hborla hborla merged commit 9a2b29b into swiftlang:master Jan 8, 2020
@hborla hborla deleted the general-ambiguity-failures branch January 8, 2020 01:34
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.

2 participants