mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
343a359109
rust/tests/ui/no-reuse-move-arc.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

20 lines
719 B
Plaintext
Raw Normal View History

update tests for migrate mode by default
2019-04-22 02:40:08 -05: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 06:04:13 -05:00
--> $DIR/no-reuse-move-arc.rs:12:16
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
update tests for migrate mode by default
2019-04-22 02:40:08 -05: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 02:40:56 -05: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 13:07:59 -05:00
LL |
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
LL | thread::spawn(move|| {
update tests for migrate mode by default
2019-04-22 02:40:08 -05: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 07:28:26 -05:00
...
Update tests
2019-03-09 06:03:44 -06: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 06:04:13 -05: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 07:28:26 -05:00
update tests for migrate mode by default
2019-04-22 02:40:08 -05:00
error: aborting due to previous error
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
For more information about this error, try `rustc --explain E0382`.
Reference in New Issue Copy Permalink