rust/tests/ui/borrowck/issue-41962.stderr

error[E0382]: use of moved value
  --> $DIR/issue-41962.rs:5:21
   |
LL |         if let Some(thing) = maybe {
   |                     ^^^^^ value moved here, in previous iteration of loop
   |
   = note: move occurs because value has type `Vec<bool>`, which does not implement the `Copy` trait
help: borrow this binding in the pattern to avoid moving the value
   |
LL |         if let Some(ref thing) = maybe {
   |                     +++

error: aborting due to previous error

For more information about this error, try `rustc --explain E0382`.
Update tests 2019-05-02 18:34:15 -04:00			`error[E0382]: use of moved value`
			`--> $DIR/issue-41962.rs:5: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 17:17:58 +02:00			`\|`
Use better spans for dummy accesses used in matches 2018-07-22 21:13:18 +01:00			`LL \| if let Some(thing) = maybe {`
Test fixes for the change of error message for issue #54015 2018-09-28 09:21:10 -07: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 17:17:58 +02:00			`\|`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 10:40:56 +03:00			= note: move occurs because value has type `Vec<bool>`, which does not implement the `Copy` trait
Suggest `.clone()` or `ref binding` on E0382 2022-11-02 21:22:24 -07:00			`help: borrow this binding in the pattern to avoid moving the value`
Provide suggestions for some moved value errors When encountering an used moved value where the previous move happened in a `match` or `if let` pattern, suggest using `ref`. Fix #63988. When encountering a `&mut` value that is used in multiple iterations of a loop, suggest reborrowing it with `&mut *`. Fix #62112. 2020-06-19 22:45:09 -07:00			`\|`
			`LL \| if let Some(ref thing) = maybe {`
Modify structured suggestion output * On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span 2021-06-21 19:07:19 -07:00			`\| +++`
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 17:17:58 +02:00
Update tests 2019-05-02 18:34:15 -04:00			`error: aborting due to previous error`
Move reason for move to label 2017-09-05 23:36:34 -07:00
update tests 2018-03-03 15:59:40 +01:00			For more information about this error, try `rustc --explain E0382`.