-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Suggest removing &mut
when encountering mutability error
#68723
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
Closed
LeSeulArtichaut
wants to merge
1
commit into
rust-lang:master
from
LeSeulArtichaut:diagnose-mut-borrow
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
// Regression test for #68697: Suggest removing `&mut x` | ||
// when `x: &mut T` and `&mut T` is expected type | ||
|
||
struct A; | ||
|
||
fn bar(x: &mut A) {} | ||
|
||
fn foo(x: &mut A) { | ||
bar(&mut x); | ||
//~^ ERROR: cannot borrow `x` as mutable | ||
//~| HELP: remove the unnecessary `&mut` here | ||
//~| SUGGESTION: x | ||
} | ||
|
||
fn main() {} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
error[E0596]: cannot borrow `x` as mutable, as it is not declared as mutable | ||
--> $DIR/issue-68697-remove-mut-ref.rs:6:9 | ||
| | ||
LL | bar(&mut x); | ||
| ^^^^^^ | ||
| | | ||
| cannot borrow as mutable | ||
| help: remove the unnecessary `&mut` here: `x` | ||
|
||
error: aborting due to previous error | ||
|
||
For more information about this error, try `rustc --explain E0596`. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
This condition seems insufficient. You'd need to check that the expected type requires
&mut T
and not&mut &mut T
, otherwise it seems like it would trigger on this (which is a good test to add, to ensure that this behaves correctly):...but this makes me wonder whether this is doable in borrowck if you don't know what type is expected (seems you only know that you want to take a mutable borrow and cannot due to lack of
mut
on the binding. On the other hand, if you do check it in typeck, then we need to check that:still compiles... which is probably not a good idea in typeck.