-
Notifications
You must be signed in to change notification settings - Fork 13.3k
1.17 nightly Compiler suggests wrong syntax mut mut var
#40823
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
I think this was introduced in #40445 |
arielb1
added a commit
to arielb1/rust
that referenced
this issue
Mar 26, 2017
This converts all of borrowck's `mut` suggestions to a new `mc::ImmutabilityBlame` API instead of the current mix of various hacks. Fixes rust-lang#35937. Fixes rust-lang#40823.
Also other incorrect mut changes are suggested:
which is also not valid and should be This happens with:
|
#40859 shows a similar bad suggestion even on stable. So maybe that problem has existed for a while, and the cases here just weren't making suggestions at all until recent nightlies. |
frewsxcv
added a commit
to frewsxcv/rust
that referenced
this issue
Mar 29, 2017
borrowck: consolidate `mut` suggestions This converts all of borrowck's `mut` suggestions to a new `mc::ImmutabilityBlame` API instead of the current mix of various hacks. Fixes rust-lang#35937. Fixes rust-lang#40823. Fixes rust-lang#40859. cc @estebank r? @pnkfelix
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
When trying to compile
the compiler rustc 1.17.0-nightly (3da4023 2017-03-24) throws an error together with a helpful suggestion
Here, the
mut mut buf
is obviously very very wrong. The stable and beta compilers don't suffer from this issue (they just provide no „consider …“ message at all).The text was updated successfully, but these errors were encountered: