-
-
Notifications
You must be signed in to change notification settings - Fork 486
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
cannot borrow *self
as immutable
#561
Comments
@matthewjasper is this behaviour intended? Is it a legitimate error of the nalgebra crate? |
Hi! Thank you for reporting this and for the fix. I find this warning strange, so I prefer to wait for what @matthewjasper has to say about it before merging anything. Also keep in mind we don't intend to support rust 2015 indefinitely so at some point in the future rust 2018 will likely be necessary for using nalgebra (e.g. whenever specialization and const-generics land). |
Yes, this is intended. It's the result of fixing rust-lang/rust#27868 . |
Yeah, so I guess I'd ask my PR to get merged then. |
This might already arrive in nightlies in next week. The sooner a fixed version is available on crates.io, the better. |
This gets us a fix for a forward compat compiler warning for the upcoming NLL enabling on the 2015 edition. See dimforge/nalgebra#561
Hi, as I'm seeing Rust developers getting serious about enabling the new borrow checker on the 2015 edition (rust-lang/rust#57804 / rust-lang/rust#59114), I compiled my local project with
RUSTFLAGS="-Zborrowck=migrate -Ztwo-phase-borrows" cargo +nightly check
to test for any possible future problems.When it compiled
nalgebra 0.16.13
for me, I got multiple newly introduced compiler warnings. Even on nalgebra master, I'm getting one compiler warning:I'd love a fix of the issue and a new crates.io release soon after that. Thanks!
The text was updated successfully, but these errors were encountered: