-
Notifications
You must be signed in to change notification settings - Fork 13.4k
proc macro 1.1 error messages spew massive amounts of junk #38586
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
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
P-medium
Medium priority
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
cc @erickt |
I think we could basically never show source spans for proc macro source code. And/or always show the use site, rather than the def site. |
@jseyfried says he'll take a look when he gets back from vacation |
triage: P-medium |
Fixed in #38792. |
Thank you so much @jseyfried ! This is good polish. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
P-medium
Medium priority
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
This is an example of an error message I got with serde and serde_derive 0.8.20 on a recent nightly. As pasted here it doesn't look horrific, but it consists of massive lines of garbage and whitespace that wordwrap on the console to create a nonsense maelstrom.
Even if we accept that the error messages must be bad, I think we can do considerably better than this. This is scheduled to be stable with 1.15 in feb. Can we fix this up before?
cc @nrc @jonathandturner
The text was updated successfully, but these errors were encountered: