-
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
Rustc does not stop on error. #31804
Labels
A-parser
Area: The parsing of Rust source code to an AST
P-high
High priority
regression-from-stable-to-beta
Performance or correctness regression from stable to beta.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
Aatch
added
A-parser
Area: The parsing of Rust source code to an AST
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
labels
Feb 22, 2016
cc @nrc I think this is actually a feature. |
@eddyb What do you mean by feature? The Compiler does not stop. It spins three cores. |
@KalitaAlexey so it does this in a loop? My bad, I didn't understand. |
arielb1
added
the
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
label
Mar 1, 2016
We got to fix that in beta. |
triage: P-high |
Introduced by #31555, according to a bisect. |
Reassigning to @nrc now that he's back |
sfackler
added
regression-from-stable-to-beta
Performance or correctness regression from stable to beta.
and removed
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
labels
Mar 24, 2016
pnkfelix
pushed a commit
to pnkfelix/rust
that referenced
this issue
Apr 7, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-parser
Area: The parsing of Rust source code to an AST
P-high
High priority
regression-from-stable-to-beta
Performance or correctness regression from stable to beta.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
It outputs
again and again. It does not stop.
The text was updated successfully, but these errors were encountered: