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

Make -Z treat-err-as-bug accept a number of errors to skip #58983

Closed
estebank opened this issue Mar 7, 2019 · 0 comments
Closed

Make -Z treat-err-as-bug accept a number of errors to skip #58983

estebank opened this issue Mar 7, 2019 · 0 comments
Labels
B-unstable Blocker: Implemented in the nightly compiler and unstable. C-feature-request Category: A feature request, i.e: not implemented / a PR. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@estebank
Copy link
Contributor

estebank commented Mar 7, 2019

Allow -Z treat-err-as-bug to take a number, in order to make it easier to debug errors that can't be made to be emitted first. In my mind, you'd call rustc -Z treat-err-as-bug 2 on a file with three errors and the first two would be emitted, you'd get the backtrace for the second one, and the third one wouldn't be emitted.

@estebank estebank added T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. B-unstable Blocker: Implemented in the nightly compiler and unstable. C-feature-request Category: A feature request, i.e: not implemented / a PR. labels Mar 7, 2019
pietroalbini added a commit to pietroalbini/rust that referenced this issue Mar 8, 2019
…oli-obk

Teach `-Z treat-err-as-bug` to take a number of errors to emit

`-Z treat-err-as-bug` will cause `rustc` to panic after the first error is reported, like previously. `-Z treat-err-as-bug=2` will cause `rustc` to panic after 2 errors have been reported.

Fix rust-lang#58983.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B-unstable Blocker: Implemented in the nightly compiler and unstable. C-feature-request Category: A feature request, i.e: not implemented / a PR. T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

1 participant