Skip to content
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

report the total number of errors on compilation failure #43015

Merged
merged 2 commits into from
Jul 2, 2017

Conversation

arielb1
Copy link
Contributor

@arielb1 arielb1 commented Jul 2, 2017

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

@arielb1 arielb1 added the relnotes Marks issues that should be documented in the release notes of the next release. label Jul 2, 2017
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.
@eddyb
Copy link
Member

eddyb commented Jul 2, 2017

@bors r+

@bors
Copy link
Contributor

bors commented Jul 2, 2017

📌 Commit fb7ab9e has been approved by eddyb

bors added a commit that referenced this pull request Jul 2, 2017
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
@bors
Copy link
Contributor

bors commented Jul 2, 2017

⌛ Testing commit fb7ab9e with merge 2a99216...

@bors
Copy link
Contributor

bors commented Jul 2, 2017

☀️ Test successful - status-appveyor, status-travis
Approved by: eddyb
Pushing 2a99216 to master...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
relnotes Marks issues that should be documented in the release notes of the next release.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants