3 ms·
I wonder how clear error messages for this kind of liveness checking will be. Will they be able to point to variable usage that causes a variable to be locked?
by sspiff 10y ago
I wonder how clear error messages for this kind of liveness checking will be. Will they be able to point to variable usage that causes a variable to be locked?
- chrismorgan 10y agoThe Rust team is committed to having high-quality error messages in rustc, and its lifetime error messages are singularly superb, making a complex concept understandable and explaining in very thorough detail when necessary what is causing a problem: “this expected this because of this but found this which would mean that instead” with detailed diagnostics of the points in question, and such things. This tradition will not be forsaken with non-lexical lifetimes.
- cmrx64 10y agoI don't think anyone cares more about good error messages for this class of errors than Niko. The error messages are already pretty good today, pointing to precisely where a location was borrowed, and I'm sure it won't be allowed to regress, only improve.
- killercup 10y agoJust yesterday an overhaul of the style of the error messages landed (should be in the next nightly). It doesn't change the actual messages, but should make thinks like scopes clearer. You can find a few screenshots in the PR: https://github.com/rust-lang/rust/pull/32756#issuecomment-207095555 https://github.com/rust-lang/rust/pull/32756#issuecomment-20...