cc80106cb5
When encountering multiple mutable borrows, suggest cloning and adding
derive annotations as needed.
```
error[E0596]: cannot borrow `sm.x` as mutable, as it is behind a `&` reference
--> $DIR/accidentally-cloning-ref-borrow-error.rs:32:9
|
LL | foo(&mut sm.x);
| ^^^^^^^^^ `sm` is a `&` reference, so the data it refers to cannot be borrowed as mutable
|
help: `Str` doesn't implement `Clone`, so this call clones the reference `&Str`
--> $DIR/accidentally-cloning-ref-borrow-error.rs:31:21
|
LL | let mut sm = sr.clone();
| ^^^^^^^
help: consider annotating `Str` with `#[derive(Clone)]`
|
LL + #[derive(Clone)]
LL | struct Str {
|
help: consider specifying this binding's type
|
LL | let mut sm: &mut Str = sr.clone();
| ++++++++++
```
```
error[E0596]: cannot borrow `*inner` as mutable, as it is behind a `&` reference
--> $DIR/issue-91206.rs:14:5
|
LL | inner.clear();
| ^^^^^ `inner` is a `&` reference, so the data it refers to cannot be borrowed as mutable
|
help: you can `clone` the `Vec<usize>` value and consume it, but this might not be your desired behavior
--> $DIR/issue-91206.rs:11:17
|
LL | let inner = client.get_inner_ref();
| ^^^^^^^^^^^^^^^^^^^^^^
help: consider specifying this binding's type
|
LL | let inner: &mut Vec<usize> = client.get_inner_ref();
| +++++++++++++++++
```
20 lines
734 B
Plaintext
20 lines
734 B
Plaintext
error[E0596]: cannot borrow `*inner` as mutable, as it is behind a `&` reference
|
|
--> $DIR/issue-91206.rs:14:5
|
|
|
|
|
LL | inner.clear();
|
|
| ^^^^^ `inner` is a `&` reference, so the data it refers to cannot be borrowed as mutable
|
|
|
|
|
help: you can `clone` the `Vec<usize>` value and consume it, but this might not be your desired behavior
|
|
--> $DIR/issue-91206.rs:11:17
|
|
|
|
|
LL | let inner = client.get_inner_ref();
|
|
| ^^^^^^^^^^^^^^^^^^^^^^
|
|
help: consider specifying this binding's type
|
|
|
|
|
LL | let inner: &mut Vec<usize> = client.get_inner_ref();
|
|
| +++++++++++++++++
|
|
|
|
error: aborting due to 1 previous error
|
|
|
|
For more information about this error, try `rustc --explain E0596`.
|