rust/src/test/ui/borrowck/issue-41962.stderr

error[E0382]: use of partially moved value: `maybe` (Ast)
  --> $DIR/issue-41962.rs:17:30
   |
LL |         if let Some(thing) = maybe {
   |                     -----    ^^^^^ value used here after move
   |                     |
   |                     value moved here
   |
   = note: move occurs because the value has type `std::vec::Vec<bool>`, which does not implement the `Copy` trait

error[E0382]: use of moved value: `(maybe as std::prelude::v1::Some).0` (Ast)
  --> $DIR/issue-41962.rs:17:21
   |
LL |         if let Some(thing) = maybe {
   |                     ^^^^^ value moved here in previous iteration of loop
   |
   = note: move occurs because the value has type `std::vec::Vec<bool>`, which does not implement the `Copy` trait

error[E0382]: use of moved value (Mir)
  --> $DIR/issue-41962.rs:17:21
   |
LL |         if let Some(thing) = maybe {
   |                     ^^^^^ value moved here in previous iteration of loop
   |
   = note: move occurs because value has type `std::vec::Vec<bool>`, which does not implement the `Copy` trait

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0382`.
Add mir test, review comments 2018-01-03 15:55:40 -06:00			error[E0382]: use of partially moved value: `maybe` (Ast)
			`--> $DIR/issue-41962.rs:17:30`
Move reason for move to label 2017-09-06 01:36:34 -05:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| if let Some(thing) = maybe {`
Move reason for move to label 2017-09-06 01:36:34 -05:00			`\| ----- ^^^^^ value used here after move`
			`\| \|`
Be ambiguous when type cannot be properly mentioned 2018-01-02 00:23:13 -06:00			`\| value moved here`
			`\|`
			= note: move occurs because the value has type `std::vec::Vec<bool>`, which does not implement the `Copy` trait
Move reason for move to label 2017-09-06 01:36:34 -05:00
Add mir test, review comments 2018-01-03 15:55:40 -06:00			error[E0382]: use of moved value: `(maybe as std::prelude::v1::Some).0` (Ast)
			`--> $DIR/issue-41962.rs:17:21`
Move reason for move to label 2017-09-06 01:36:34 -05:00			`\|`
Update UI tests 2018-02-22 18:42:32 -06:00			`LL \| if let Some(thing) = maybe {`
Address review comments: make label shorter 2018-01-02 00:10:04 -06:00			`\| ^^^^^ value moved here in previous iteration of loop`
Be ambiguous when type cannot be properly mentioned 2018-01-02 00:23:13 -06:00			`\|`
			= note: move occurs because the value has type `std::vec::Vec<bool>`, which does not implement the `Copy` trait
Move reason for move to label 2017-09-06 01:36:34 -05:00
Update tests that use `-Z borrowck=compare` or `#[feature(nll)]` to accmmodate diagnostic change. 2018-07-31 07:36:50 -05:00			`error[E0382]: use of moved value (Mir)`
			`--> $DIR/issue-41962.rs:17:21`
rust-lang/rust#41962 has a new error with my new code. Incorporate that into my code. In particular, I am adding an implicit injected borrow on the pattern matches, and when we go around the loop, the compiler is reporting that this injected borrow is conflicting with the move of the original value when the match succeeds. 2018-05-09 10:17:58 -05:00			`\|`
Use better spans for dummy accesses used in matches 2018-07-22 15:13:18 -05:00			`LL \| if let Some(thing) = maybe {`
Update tests that use `-Z borrowck=compare` or `#[feature(nll)]` to accmmodate diagnostic change. 2018-07-31 07:36:50 -05:00			`\| ^^^^^ value moved here in previous iteration of loop`
rust-lang/rust#41962 has a new error with my new code. Incorporate that into my code. In particular, I am adding an implicit injected borrow on the pattern matches, and when we go around the loop, the compiler is reporting that this injected borrow is conflicting with the move of the original value when the match succeeds. 2018-05-09 10:17:58 -05:00			`\|`
Fix erroneous error note when using field after move 2018-06-20 21:51:18 -05:00			= note: move occurs because value has type `std::vec::Vec<bool>`, which does not implement the `Copy` trait
rust-lang/rust#41962 has a new error with my new code. Incorporate that into my code. In particular, I am adding an implicit injected borrow on the pattern matches, and when we go around the loop, the compiler is reporting that this injected borrow is conflicting with the move of the original value when the match succeeds. 2018-05-09 10:17:58 -05:00
De-duplicate moved variable errors. By introducing a new map that tracks the errors reported and the `Place`s that spawned those errors against the move out that the error was referring to, we are able to silence duplicate errors by emitting only the error which corresponds to the most specific `Place` (that which other `Place`s which reported errors are prefixes of). This generally is an improvement, however there is a case - `liveness-move-in-while` - where the output regresses. 2018-09-06 08:48:33 -05:00			`error: aborting due to 3 previous errors`
Move reason for move to label 2017-09-06 01:36:34 -05:00
update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0382`.