-
Notifications
You must be signed in to change notification settings - Fork 13k
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
try to ensure all errors use spans #444
Comments
I could only find one instance of sess.err that should have been sess.span_err, which I just committed a fix for. Otherwise, instances of ".err" are either invocations of the err method on a parser or reader object, which already use span_err, or they're errors along the lines of "multiple main fns defined" or "no input filename given", for which span doesn't make sense. See anything I missed? |
There are also plenty of places that just use fail directly and should be using span_err. I know extfmt does this. |
Should we have a policy that every fail should be replaced by a sess.span_err (or sess.unimpl or sess.bug)? |
lkuper: I think so |
sess.span_err instead of 'fail'. (issue #444)
sess.span_err instead of 'fail'. (issue rust-lang#444)
I can't find any fatal's or errors that should have spans but don't |
add pledge(2) syscall.
This is already included with the regular stability attributes, and some of this is now stable, while some of it is not.
Referenceify conditional compilation
ci: add support for loongarch64-unknown-linux-gnu
We have a bunch of cases of sess.err in the code that ought to be sess.span_err -- that is, they should carry a source position indicating the origin of the error. Fix these.
The text was updated successfully, but these errors were encountered: