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

rustc shouldn't stop after the first error #440

Closed
pcwalton opened this issue Jun 1, 2011 · 2 comments
Closed

rustc shouldn't stop after the first error #440

pcwalton opened this issue Jun 1, 2011 · 2 comments
Labels
A-driver Area: rustc_driver that ties everything together into the `rustc` compiler

Comments

@pcwalton
Copy link
Contributor

pcwalton commented Jun 1, 2011

After the first error, we should keep going in some cases. As a first stab at this, we could abandon the current function and try to resolve/typecheck other functions.

brson added a commit that referenced this issue Jun 19, 2011
These errors are non-fatal. The session.abort_if_errors function needs to be
called at strategic points to convert the previous errors to utter failure.

Issue #440
brson added a commit that referenced this issue Jun 19, 2011
Failure happens at the end of import resolution

Issue #440
brson added a commit that referenced this issue Jun 19, 2011
Failure happens at the end of name resolution

Issue #440
brson added a commit that referenced this issue Jun 19, 2011
These errors are non-fatal. The session.abort_if_errors function needs to be
called at strategic points to convert the previous errors to utter failure.

Issue #440
brson added a commit that referenced this issue Jun 19, 2011
Failure happens at the end of import resolution

Issue #440
brson added a commit that referenced this issue Jun 19, 2011
Failure happens at the end of name resolution

Issue #440
@ghost ghost assigned brson Jun 27, 2011
brson added a commit that referenced this issue Jul 5, 2011
Add a failure checkpoint after the typechecking pass. There are still many
fatal errors in typeck, but loosening up this one makes it easier to lean on
the compiler when making changes to types.

Issue #440.
@brson
Copy link
Contributor

brson commented Sep 27, 2011

So there is a mechanism for this now and a lot of the most frequent errors are non-fatal, but I'm unassigning myself because I don't have any plans for 'finishing' this task.

@graydon
Copy link
Contributor

graydon commented Dec 5, 2011

if a mechanism exists and we are actively using it, i am ok closing the bug.

@graydon graydon closed this as completed Dec 5, 2011
keeperofdakeys pushed a commit to keeperofdakeys/rust that referenced this issue Dec 12, 2017
kazcw pushed a commit to kazcw/rust that referenced this issue Oct 23, 2018
dlrobertson pushed a commit to dlrobertson/rust that referenced this issue Nov 29, 2018
ZuseZ4 pushed a commit to EnzymeAD/rust that referenced this issue Mar 7, 2023
GuillaumeGomez pushed a commit to GuillaumeGomez/rust that referenced this issue Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-driver Area: rustc_driver that ties everything together into the `rustc` compiler
Projects
None yet
Development

No branches or pull requests

3 participants