-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
New errors: expected/found types omitted #33366
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
Comments
/cc @nikomatsakis |
Ah, I can see that this is because both types are "primitive", i.e. bool/char/int/float. In this case Previously, for these cases the "inner type error" in parens was omitted - which appears to be omitted in all cases now. I think the |
birkenfeld
added a commit
to birkenfeld/rust
that referenced
this issue
May 3, 2016
Previously, the second "expected X, found Y" in parens was omitted for simple errors because it added no information. Now that this is always omitted, there is no need for a distinction anymore. This change restores the "expected, found" message for such errors. Fixes: rust-lang#33366
bors
added a commit
that referenced
this issue
May 19, 2016
Fix for old school error issues, improvements to new school This PR: * Fixes some old school error issues, specifically #33559, #33543, #33366 * Improves wording borrowck errors with match patterns * De-emphasize multi-line spans, so we don't color the single source character when we're trying to say "span starts here" * Rollup of #33392 (which should help fix #33390) r? @nikomatsakis
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found this when I wanted to see how the new errors look. (If this is still expected to be WIP, let me know and I won't report other such cases for a while.)
In this test case, the "expected/found" notes don't appear:
The text was updated successfully, but these errors were encountered: