rust/src/test/ui/nll/issue-53807.stderr

error[E0382]: use of moved value
  --> $DIR/issue-53807.rs:4: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 field in the pattern to avoid moving `maybe.0`
   |
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 for migrate mode by default 2019-04-22 02:40:08 -05:00			`error[E0382]: use of moved value`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-53807.rs:4:21`
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			`\|`
			`LL \| if let Some(thing) = maybe {`
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`\| ^^^^^ value moved here, in previous iteration of loop`
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			`\|`
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 02:40:56 -05:00			= note: move occurs because value has type `Vec<bool>`, which does not implement the `Copy` trait
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-20 00:45:09 -05:00			help: borrow this field in the pattern to avoid moving `maybe.0`
			`\|`
			`LL \| if let Some(ref thing) = maybe {`
			`\| ^^^`
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
update tests for migrate mode by default 2019-04-22 02:40:08 -05:00			`error: aborting due to previous error`
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
			For more information about this error, try `rustc --explain E0382`.