-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
request: report the number of compilation errors #42793
Comments
Nominating for compiler team: we should make a decision here and stick to it, and I'm inclined to say that restoring the old functionality also leads to reports of incorrect numbering. If we can fix the numbering (easily) then I'm all for it though, but last I looked this wasn't an easy task. |
If completely fixing the numbers is non-trivial, is it feasible/acceptable to report "There were at least 10 errors"? Or is the count so buggy we don't even know a minimum? |
IIRC, I saw an issue recently about the returned value being 3 where it should've been 1, so I don't think that's true. It's possible that was due to old code though. |
triage: P-medium My feeling is that if we can get a correct count, that would be good. This doesn't seem too hard in principle, but I guess there are... obstacles. |
Prior to this PR, when we aborted because a "critical pass" failed, we displayed the number of errors from that critical pass. While that's the number of errors that caused compilation to abort in *that place*, that's not what people really want to know. Instead, always report the total number of errors, and don't bother to track the number of errors from the last pass that failed. This changes the compiler driver API to handle errors more smoothly, and therefore is a compiler-api-[breaking-change]. Fixes rust-lang#42793.
report the total number of errors on compilation failure Prior to this PR, when we aborted because a "critical pass" failed, we displayed the number of errors from that critical pass. While that's the number of errors that caused compilation to abort in *that place*, that's not what people really want to know. Instead, always report the total number of errors, and don't bother to track the number of errors from the last pass that failed. This changes the compiler driver API to handle errors more smoothly, therefore is a compiler-api-[breaking-change]. Fixes #42793. r? @eddyb
No description provided.
The text was updated successfully, but these errors were encountered: