rust/tests/ui/no-reuse-move-arc.stderr

error[E0382]: borrow of moved value: `arc_v`
  --> $DIR/no-reuse-move-arc.rs:12:16
   |
LL |     let arc_v = Arc::new(v);
   |         ----- move occurs because `arc_v` has type `Arc<Vec<i32>>`, which does not implement the `Copy` trait
LL |
LL |     thread::spawn(move|| {
   |                   ------ value moved into closure here
LL |         assert_eq!((*arc_v)[3], 4);
   |                      ----- variable moved due to use in closure
...
LL |     assert_eq!((*arc_v)[2], 3);
   |                ^^^^^^^^ value borrowed here after move
   |
   = note: borrow occurs due to deref coercion to `Vec<i32>`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0382`.
update tests for migrate mode by default 2019-04-22 07:40:08 +00:00			error[E0382]: borrow of moved value: `arc_v`
Note when a a move/borrow error is caused by a deref coercion Fixes #73268 When a deref coercion occurs, we may end up with a move error if the base value has been partially moved out of. However, we do not indicate anywhere that a deref coercion is occuring, resulting in an error message with a confusing span. This PR adds an explicit note to move errors when a deref coercion is involved. We mention the name of the type that the deref-coercion resolved to, as well as the `Deref::Target` associated type being used. 2020-07-25 11:04:13 +00:00			`--> $DIR/no-reuse-move-arc.rs:12:16`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`\|`
update tests for migrate mode by default 2019-04-22 07:40:08 +00:00			`LL \| let arc_v = Arc::new(v);`
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 07:40:56 +00:00			\| ----- move occurs because `arc_v` has type `Arc<Vec<i32>>`, which does not implement the `Copy` trait
fix one more case of trailing space 2022-06-08 18:07:59 +00:00			`LL \|`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`LL \| thread::spawn(move\|\| {`
update tests for migrate mode by default 2019-04-22 07:40:08 +00:00			`\| ------ value moved into closure here`
			`LL \| assert_eq!((*arc_v)[3], 4);`
			`\| ----- variable moved due to use in closure`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`...`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| assert_eq!((*arc_v)[2], 3);`
Note when a a move/borrow error is caused by a deref coercion Fixes #73268 When a deref coercion occurs, we may end up with a move error if the base value has been partially moved out of. However, we do not indicate anywhere that a deref coercion is occuring, resulting in an error message with a confusing span. This PR adds an explicit note to move errors when a deref coercion is involved. We mention the name of the type that the deref-coercion resolved to, as well as the `Deref::Target` associated type being used. 2020-07-25 11:04:13 +00:00			`\| ^^^^^^^^ value borrowed here after move`
			`\|`
			= note: borrow occurs due to deref coercion to `Vec<i32>`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
			For more information about this error, try `rustc --explain E0382`.