rust/src/test/ui/issues/issue-64559.stderr

error[E0382]: use of moved value: `orig`
  --> $DIR/issue-64559.rs:4:20
   |
LL |     let orig = vec![true];
   |         ---- move occurs because `orig` has type `std::vec::Vec<bool>`, which does not implement the `Copy` trait
LL |     for _val in orig {}
   |                 ----
   |                 |
   |                 `orig` moved due to this implicit call to `.into_iter()`
   |                 help: consider borrowing to avoid moving into the for loop: `&orig`
LL |     let _closure = || orig;
   |                    ^^ ---- use occurs due to use in closure
   |                    |
   |                    value used here after move
   |
note: this function consumes the receiver `self` by taking ownership of it, which moves `orig`
  --> $SRC_DIR/core/src/iter/traits/collect.rs:LL:COL
   |
LL |     fn into_iter(self) -> Self::IntoIter;
   |                  ^^^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0382`.
Fix the span used to suggest avoiding for-loop moves It was using the snippet from the "use" span, which often renders the same, but with closures that snippet is on the start of the closure where the value is captured. We should be using the snippet from the span where it was moved into the `for` loop, which is `move_span`. 2019-09-20 18:06:32 -05:00			error[E0382]: use of moved value: `orig`
			`--> $DIR/issue-64559.rs:4:20`
			`\|`
			`LL \| let orig = vec![true];`
			\| ---- move occurs because `orig` has type `std::vec::Vec<bool>`, which does not implement the `Copy` trait
			`LL \| for _val in orig {}`
			`\| ----`
			`\| \|`
Explain move errors that occur due to method calls involving `self` This is a re-attempt of #72389 (which was reverted in #73594) Instead of using `ExpnKind::Desugaring` to represent operators, this PR checks the lang item directly. 2020-06-11 12:48:46 -05:00			\| `orig` moved due to this implicit call to `.into_iter()`
Fix the span used to suggest avoiding for-loop moves It was using the snippet from the "use" span, which often renders the same, but with closures that snippet is on the start of the closure where the value is captured. We should be using the snippet from the span where it was moved into the `for` loop, which is `move_span`. 2019-09-20 18:06:32 -05:00			\| help: consider borrowing to avoid moving into the for loop: `&orig`
			`LL \| let _closure = \|\| orig;`
			`\| ^^ ---- use occurs due to use in closure`
			`\| \|`
			`\| value used here after move`
Explain move errors that occur due to method calls involving `self` This is a re-attempt of #72389 (which was reverted in #73594) Instead of using `ExpnKind::Desugaring` to represent operators, this PR checks the lang item directly. 2020-06-11 12:48:46 -05:00			`\|`
			note: this function consumes the receiver `self` by taking ownership of it, which moves `orig`
mv std libs to library/ 2020-06-11 21:31:49 -05:00			`--> $SRC_DIR/core/src/iter/traits/collect.rs:LL:COL`
Explain move errors that occur due to method calls involving `self` This is a re-attempt of #72389 (which was reverted in #73594) Instead of using `ExpnKind::Desugaring` to represent operators, this PR checks the lang item directly. 2020-06-11 12:48:46 -05:00			`\|`
			`LL \| fn into_iter(self) -> Self::IntoIter;`
			`\| ^^^^`
Fix the span used to suggest avoiding for-loop moves It was using the snippet from the "use" span, which often renders the same, but with closures that snippet is on the start of the closure where the value is captured. We should be using the snippet from the span where it was moved into the `for` loop, which is `move_span`. 2019-09-20 18:06:32 -05:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0382`.