rust/tests/ui/moves/issue-75904-move-closure-loop.stderr

error[E0382]: use of moved value: `a`
  --> $DIR/issue-75904-move-closure-loop.rs:10:9
   |
LL |     let mut a = NotCopy;
   |         ----- move occurs because `a` has type `NotCopy`, which does not implement the `Copy` trait
LL |     loop {
LL |         || {
   |         ^^ value moved into closure here, in previous iteration of loop
LL |             &mut a;
LL |             a;
   |             - use occurs due to use in closure

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0382`.
Point to a move-related span when pointing to closure upvars Fixes #75904 When emitting move/borrow errors, we may point into a closure to indicate why an upvar is used in the closure. However, we use the 'upvar span', which is just an arbitrary usage of the upvar. If the upvar is used in multiple places (e.g. a borrow and a move), we may end up pointing to the borrow. If the overall error is a move error, this can be confusing. This PR tracks the span that caused an upvar to become captured by-value instead of by-ref (assuming that it's not a `move` closure). We use this span instead of the 'upvar' span when we need to point to an upvar usage during borrow checking. 2020-08-26 03:58:58 +00:00			error[E0382]: use of moved value: `a`
			`--> $DIR/issue-75904-move-closure-loop.rs:10:9`
			`\|`
			`LL \| let mut a = NotCopy;`
			\| ----- move occurs because `a` has type `NotCopy`, which does not implement the `Copy` trait
			`LL \| loop {`
			`LL \| \|\| {`
			`\| ^^ value moved into closure here, in previous iteration of loop`
			`LL \| &mut a;`
			`LL \| a;`
			`\| - use occurs due to use in closure`

Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Point to a move-related span when pointing to closure upvars Fixes #75904 When emitting move/borrow errors, we may point into a closure to indicate why an upvar is used in the closure. However, we use the 'upvar span', which is just an arbitrary usage of the upvar. If the upvar is used in multiple places (e.g. a borrow and a move), we may end up pointing to the borrow. If the overall error is a move error, this can be confusing. This PR tracks the span that caused an upvar to become captured by-value instead of by-ref (assuming that it's not a `move` closure). We use this span instead of the 'upvar' span when we need to point to an upvar usage during borrow checking. 2020-08-26 03:58:58 +00:00
			For more information about this error, try `rustc --explain E0382`.