-
Notifications
You must be signed in to change notification settings - Fork 0
Add feature(nll) #28
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
Add feature(nll) #28
Conversation
62aa02b
to
e6c1e3b
Compare
src/librustc/session/mod.rs
Outdated
self.features.borrow().nll || self.opts.debugging_opts.nll | ||
} | ||
pub fn nll_dump_cause(&self) -> bool { | ||
self.features.borrow().nll || self.opts.debugging_opts.nll_dump_cause |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am debating whether we should have #![feature(nll)]
enable dump-cause or not. The main reason not to is that it is so sloooooow right now. I feel like we might want to enable it once we make it faster (and then we wouldn't have this switch at all.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks basically right, modulo the question about -Znll-dump-cause
, and the fact that it needs to handle -Zborrowck=mir
e6c1e3b
to
ab4070d
Compare
efa46b3
to
1ce4a8d
Compare
ab4070d
to
4615bc5
Compare
4615bc5
to
915bd0e
Compare
This should be ready! |
1ce4a8d
to
dbb21b3
Compare
In particular, -Znll might as well imply -Zborrowck=mir by default, just like `#![feature(nll)]` does. Also, if NLL is in use, no reason to emit end regions. The NLL pass just strips them out anyway.
Also, keep reporting AST-based region errors that are not occuring in a fn body.
915bd0e
to
0f41fbb
Compare
Sync to rust-lang/rust master
This is for rust-lang#46716