2020-06-11 12:48:46 -05:00
|
|
|
error[E0382]: use of moved value: `val.0`
|
|
|
|
--> $DIR/move-fn-self-receiver.rs:30:5
|
|
|
|
|
|
|
|
|
LL | val.0.into_iter().next();
|
|
|
|
| ----------- `val.0` moved due to this method call
|
|
|
|
LL | val.0;
|
|
|
|
| ^^^^^ value used here after move
|
|
|
|
|
|
2022-12-12 06:07:09 -06:00
|
|
|
note: `into_iter` takes ownership of the receiver `self`, which moves `val.0`
|
2020-06-11 21:31:49 -05:00
|
|
|
--> $SRC_DIR/core/src/iter/traits/collect.rs:LL:COL
|
2020-09-02 02:40:56 -05:00
|
|
|
= note: move occurs because `val.0` has type `Vec<bool>`, which does not implement the `Copy` trait
|
2022-12-25 18:51:11 -06:00
|
|
|
help: you can `clone` the value and consume it, but this might not be your desired behavior
|
|
|
|
|
|
|
|
|
LL | val.0.clone().into_iter().next();
|
|
|
|
| ++++++++
|
2020-06-11 12:48:46 -05:00
|
|
|
|
|
|
|
error[E0382]: use of moved value: `foo`
|
|
|
|
--> $DIR/move-fn-self-receiver.rs:34:5
|
|
|
|
|
|
|
|
|
LL | let foo = Foo;
|
|
|
|
| --- move occurs because `foo` has type `Foo`, which does not implement the `Copy` trait
|
|
|
|
LL | foo.use_self();
|
|
|
|
| ---------- `foo` moved due to this method call
|
|
|
|
LL | foo;
|
|
|
|
| ^^^ value used here after move
|
|
|
|
|
|
2022-12-12 06:07:09 -06:00
|
|
|
note: `Foo::use_self` takes ownership of the receiver `self`, which moves `foo`
|
2020-06-11 12:48:46 -05:00
|
|
|
--> $DIR/move-fn-self-receiver.rs:13:17
|
|
|
|
|
|
|
|
|
LL | fn use_self(self) {}
|
|
|
|
| ^^^^
|
|
|
|
|
|
|
|
error[E0382]: use of moved value: `second_foo`
|
|
|
|
--> $DIR/move-fn-self-receiver.rs:38:5
|
|
|
|
|
|
|
|
|
LL | let second_foo = Foo;
|
|
|
|
| ---------- move occurs because `second_foo` has type `Foo`, which does not implement the `Copy` trait
|
|
|
|
LL | second_foo.use_self();
|
|
|
|
| ---------- `second_foo` moved due to this method call
|
|
|
|
LL | second_foo;
|
|
|
|
| ^^^^^^^^^^ value used here after move
|
|
|
|
|
|
|
|
error[E0382]: use of moved value: `boxed_foo`
|
|
|
|
--> $DIR/move-fn-self-receiver.rs:42:5
|
|
|
|
|
|
|
|
|
LL | let boxed_foo = Box::new(Foo);
|
2020-09-02 02:40:56 -05:00
|
|
|
| --------- move occurs because `boxed_foo` has type `Box<Foo>`, which does not implement the `Copy` trait
|
2020-06-11 12:48:46 -05:00
|
|
|
LL | boxed_foo.use_box_self();
|
|
|
|
| -------------- `boxed_foo` moved due to this method call
|
|
|
|
LL | boxed_foo;
|
|
|
|
| ^^^^^^^^^ value used here after move
|
|
|
|
|
|
2022-12-12 06:07:09 -06:00
|
|
|
note: `Foo::use_box_self` takes ownership of the receiver `self`, which moves `boxed_foo`
|
2020-06-11 12:48:46 -05:00
|
|
|
--> $DIR/move-fn-self-receiver.rs:14:21
|
|
|
|
|
|
|
|
|
LL | fn use_box_self(self: Box<Self>) {}
|
|
|
|
| ^^^^
|
|
|
|
|
|
|
|
error[E0382]: use of moved value: `pin_box_foo`
|
|
|
|
--> $DIR/move-fn-self-receiver.rs:46:5
|
|
|
|
|
|
|
|
|
LL | let pin_box_foo = Box::pin(Foo);
|
2020-09-02 02:40:56 -05:00
|
|
|
| ----------- move occurs because `pin_box_foo` has type `Pin<Box<Foo>>`, which does not implement the `Copy` trait
|
2020-06-11 12:48:46 -05:00
|
|
|
LL | pin_box_foo.use_pin_box_self();
|
|
|
|
| ------------------ `pin_box_foo` moved due to this method call
|
|
|
|
LL | pin_box_foo;
|
|
|
|
| ^^^^^^^^^^^ value used here after move
|
|
|
|
|
|
2022-12-12 06:07:09 -06:00
|
|
|
note: `Foo::use_pin_box_self` takes ownership of the receiver `self`, which moves `pin_box_foo`
|
2020-06-11 12:48:46 -05:00
|
|
|
--> $DIR/move-fn-self-receiver.rs:15:25
|
|
|
|
|
|
|
|
|
LL | fn use_pin_box_self(self: Pin<Box<Self>>) {}
|
|
|
|
| ^^^^
|
|
|
|
|
|
|
|
error[E0505]: cannot move out of `mut_foo` because it is borrowed
|
|
|
|
--> $DIR/move-fn-self-receiver.rs:50:5
|
|
|
|
|
|
2023-01-16 20:52:43 -06:00
|
|
|
LL | let mut mut_foo = Foo;
|
|
|
|
| ----------- binding `mut_foo` declared here
|
2020-06-11 12:48:46 -05:00
|
|
|
LL | let ret = mut_foo.use_mut_self();
|
Use larger span for adjustments on method calls
Currently, we use a relatively 'small' span for THIR
expressions generated by an 'adjustment' (e.g. an autoderef,
autoborrow, unsizing). As a result, if a borrow generated
by an adustment ends up causing a borrowcheck error, for example:
```rust
let mut my_var = String::new();
let my_ref = &my_var
my_var.push('a');
my_ref;
```
then the span for the mutable borrow may end up referring
to only the base expression (e.g. `my_var`), rather than
the method call which triggered the mutable borrow
(e.g. `my_var.push('a')`)
Due to a quirk of the MIR borrowck implementation,
this doesn't always get exposed in migration mode,
but it does in many cases.
This commit makes THIR building consistently use 'larger'
spans for adjustment expressions
The intent of this change it make it clearer to users
when it's the specific way in which a variable is
used (for example, in a method call) that produdes
a borrowcheck error. For example, an error message
claiming that a 'mutable borrow occurs here' might
be confusing if it just points at a usage of a variable
(e.g. `my_var`), when no `&mut` is in sight. Pointing
at the entire expression should help to emphasize
that the method call itself is responsible for
the mutable borrow.
In several cases, this makes the `#![feature(nll)]` diagnostic
output match up exactly with the default (migration mode) output.
As a result, several `.nll.stderr` files end up getting removed
entirely.
2021-09-16 15:01:22 -05:00
|
|
|
| ---------------------- borrow of `mut_foo` occurs here
|
2020-06-11 12:48:46 -05:00
|
|
|
LL | mut_foo;
|
|
|
|
| ^^^^^^^ move out of `mut_foo` occurs here
|
|
|
|
LL | ret;
|
|
|
|
| --- borrow later used here
|
|
|
|
|
|
|
|
error[E0382]: use of moved value: `rc_foo`
|
|
|
|
--> $DIR/move-fn-self-receiver.rs:55:5
|
|
|
|
|
|
|
|
|
LL | let rc_foo = Rc::new(Foo);
|
2020-09-02 02:40:56 -05:00
|
|
|
| ------ move occurs because `rc_foo` has type `Rc<Foo>`, which does not implement the `Copy` trait
|
2020-06-11 12:48:46 -05:00
|
|
|
LL | rc_foo.use_rc_self();
|
|
|
|
| ------------- `rc_foo` moved due to this method call
|
|
|
|
LL | rc_foo;
|
|
|
|
| ^^^^^^ value used here after move
|
|
|
|
|
|
2022-12-12 06:07:09 -06:00
|
|
|
note: `Foo::use_rc_self` takes ownership of the receiver `self`, which moves `rc_foo`
|
2020-06-11 12:48:46 -05:00
|
|
|
--> $DIR/move-fn-self-receiver.rs:16:20
|
|
|
|
|
|
|
|
|
LL | fn use_rc_self(self: Rc<Self>) {}
|
|
|
|
| ^^^^
|
2022-12-25 18:51:11 -06:00
|
|
|
help: you can `clone` the value and consume it, but this might not be your desired behavior
|
|
|
|
|
|
|
|
|
LL | rc_foo.clone().use_rc_self();
|
|
|
|
| ++++++++
|
2020-06-11 12:48:46 -05:00
|
|
|
|
|
|
|
error[E0382]: use of moved value: `foo_add`
|
|
|
|
--> $DIR/move-fn-self-receiver.rs:59:5
|
|
|
|
|
|
|
|
|
LL | let foo_add = Foo;
|
|
|
|
| ------- move occurs because `foo_add` has type `Foo`, which does not implement the `Copy` trait
|
|
|
|
LL | foo_add + Foo;
|
|
|
|
| ------------- `foo_add` moved due to usage in operator
|
|
|
|
LL | foo_add;
|
|
|
|
| ^^^^^^^ value used here after move
|
|
|
|
|
|
|
|
|
note: calling this operator moves the left-hand side
|
2022-12-12 09:36:08 -06:00
|
|
|
--> $SRC_DIR/core/src/ops/arith.rs:LL:COL
|
2020-06-11 12:48:46 -05:00
|
|
|
|
|
|
|
error[E0382]: use of moved value: `implicit_into_iter`
|
|
|
|
--> $DIR/move-fn-self-receiver.rs:63:5
|
|
|
|
|
|
|
|
|
LL | let implicit_into_iter = vec![true];
|
2020-09-02 02:40:56 -05:00
|
|
|
| ------------------ move occurs because `implicit_into_iter` has type `Vec<bool>`, which does not implement the `Copy` trait
|
2020-06-11 12:48:46 -05:00
|
|
|
LL | for _val in implicit_into_iter {}
|
2022-03-01 22:30:16 -06:00
|
|
|
| ------------------ `implicit_into_iter` moved due to this implicit call to `.into_iter()`
|
2020-06-11 12:48:46 -05:00
|
|
|
LL | implicit_into_iter;
|
|
|
|
| ^^^^^^^^^^^^^^^^^^ value used here after move
|
2022-03-01 22:30:16 -06:00
|
|
|
|
|
|
|
|
help: consider iterating over a slice of the `Vec<bool>`'s content to avoid moving into the `for` loop
|
|
|
|
|
|
|
|
|
LL | for _val in &implicit_into_iter {}
|
|
|
|
| +
|
2020-06-11 12:48:46 -05:00
|
|
|
|
|
|
|
error[E0382]: use of moved value: `explicit_into_iter`
|
|
|
|
--> $DIR/move-fn-self-receiver.rs:67:5
|
|
|
|
|
|
|
|
|
LL | let explicit_into_iter = vec![true];
|
2020-09-02 02:40:56 -05:00
|
|
|
| ------------------ move occurs because `explicit_into_iter` has type `Vec<bool>`, which does not implement the `Copy` trait
|
2020-06-11 12:48:46 -05:00
|
|
|
LL | for _val in explicit_into_iter.into_iter() {}
|
|
|
|
| ----------- `explicit_into_iter` moved due to this method call
|
|
|
|
LL | explicit_into_iter;
|
|
|
|
| ^^^^^^^^^^^^^^^^^^ value used here after move
|
2022-11-02 23:22:24 -05:00
|
|
|
|
|
2022-12-25 18:51:11 -06:00
|
|
|
help: you can `clone` the value and consume it, but this might not be your desired behavior
|
|
|
|
|
|
|
|
|
LL | for _val in explicit_into_iter.clone().into_iter() {}
|
|
|
|
| ++++++++
|
2020-06-11 12:48:46 -05:00
|
|
|
|
|
|
|
error[E0382]: use of moved value: `container`
|
|
|
|
--> $DIR/move-fn-self-receiver.rs:71:5
|
|
|
|
|
|
|
|
|
LL | let container = Container(vec![]);
|
|
|
|
| --------- move occurs because `container` has type `Container`, which does not implement the `Copy` trait
|
|
|
|
LL | for _val in container.custom_into_iter() {}
|
|
|
|
| ------------------ `container` moved due to this method call
|
|
|
|
LL | container;
|
|
|
|
| ^^^^^^^^^ value used here after move
|
|
|
|
|
|
2022-12-12 06:07:09 -06:00
|
|
|
note: `Container::custom_into_iter` takes ownership of the receiver `self`, which moves `container`
|
2020-06-11 12:48:46 -05:00
|
|
|
--> $DIR/move-fn-self-receiver.rs:23:25
|
|
|
|
|
|
|
|
|
LL | fn custom_into_iter(self) -> impl Iterator<Item = bool> {
|
|
|
|
| ^^^^
|
|
|
|
|
2020-12-22 21:15:40 -06:00
|
|
|
error[E0382]: use of moved value: `foo2`
|
|
|
|
--> $DIR/move-fn-self-receiver.rs:75:9
|
|
|
|
|
|
|
|
|
LL | let foo2 = Foo;
|
|
|
|
| ---- move occurs because `foo2` has type `Foo`, which does not implement the `Copy` trait
|
|
|
|
LL | loop {
|
2022-11-02 23:22:24 -05:00
|
|
|
| ---- inside of this loop
|
2020-12-22 21:15:40 -06:00
|
|
|
LL | foo2.use_self();
|
|
|
|
| ^^^^ ---------- `foo2` moved due to this method call, in previous iteration of loop
|
|
|
|
|
|
|
|
error: aborting due to 12 previous errors
|
2020-06-11 12:48:46 -05:00
|
|
|
|
|
|
|
Some errors have detailed explanations: E0382, E0505.
|
|
|
|
For more information about an error, try `rustc --explain E0382`.
|