rust/tests/ui/nll/move-subpaths-moves-root.stderr

error[E0382]: use of partially moved value: `x`
  --> $DIR/move-subpaths-moves-root.rs:4:10
   |
LL |     drop(x.0);
   |          --- value partially moved here
LL |     drop(x);
   |          ^ value used here after partial move
   |
   = note: partial move occurs because `x.0` has type `Vec<i32>`, which does not implement the `Copy` trait

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0382`.
Be consistent when describing a move as a 'partial' in diagnostics When an error occurs due to a partial move, we would use the world "partial" in some parts of the error message, but not in others. This commit ensures that we use the word 'partial' in either all or none of the diagnostic messages. Additionally, we no longer describe a move out of a `Box` via `*` as a 'partial move'. This was a pre-existing issue, but became more noticable when the word 'partial' is used in more places. 2020-08-08 12:16:43 -05:00			error[E0382]: use of partially moved value: `x`
Remove feature(nll) when compare mode is sufficient 2019-04-07 10:07:36 -05:00			`--> $DIR/move-subpaths-moves-root.rs:4:10`
Inspect parents paths when checking for moves 2018-09-15 10:29:29 -05:00			`\|`
			`LL \| drop(x.0);`
Be consistent when describing a move as a 'partial' in diagnostics When an error occurs due to a partial move, we would use the world "partial" in some parts of the error message, but not in others. This commit ensures that we use the word 'partial' in either all or none of the diagnostic messages. Additionally, we no longer describe a move out of a `Box` via `*` as a 'partial move'. This was a pre-existing issue, but became more noticable when the word 'partial' is used in more places. 2020-08-08 12:16:43 -05:00			`\| --- value partially moved here`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| drop(x);`
error output updated by ./x.py test --stage 1 src/test/ui --incremental --bless 2019-02-06 09:42:21 -06:00			`\| ^ value used here after partial move`
Inspect parents paths when checking for moves 2018-09-15 10:29:29 -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: partial move occurs because `x.0` has type `Vec<i32>`, which does not implement the `Copy` trait
Inspect parents paths when checking for moves 2018-09-15 10:29:29 -05:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 09:44:16 -06:00			`error: aborting due to 1 previous error`
Inspect parents paths when checking for moves 2018-09-15 10:29:29 -05:00
			For more information about this error, try `rustc --explain E0382`.