mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
a8aa6878f6
rust/tests/ui/borrowck/move-from-union-field-issue-66500.stderr

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

28 lines
1.1 KiB
Plaintext
Raw Normal View History

Don't suppress move errors for union fields
2019-12-15 05:08:43 -06:00
error[E0507]: cannot move out of `*u.a` which is behind a shared reference
remove untagged_union feature gate
2022-06-29 21:33:18 -05:00
--> $DIR/move-from-union-field-issue-66500.rs:12:5
Don't suppress move errors for union fields
2019-12-15 05:08:43 -06:00
|
LL | *u.a
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 `*u.a` has type `String`, which does not implement the `Copy` trait
Don't suppress move errors for union fields
2019-12-15 05:08:43 -06:00
error[E0507]: cannot move out of `*u.b` which is behind a mutable reference
remove untagged_union feature gate
2022-06-29 21:33:18 -05:00
--> $DIR/move-from-union-field-issue-66500.rs:16:5
Don't suppress move errors for union fields
2019-12-15 05:08:43 -06:00
|
LL | *u.b
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 `*u.b` has type `String`, which does not implement the `Copy` trait
Don't suppress move errors for union fields
2019-12-15 05:08:43 -06:00
error[E0507]: cannot move out of `*u.c` which is behind a raw pointer
remove untagged_union feature gate
2022-06-29 21:33:18 -05:00
--> $DIR/move-from-union-field-issue-66500.rs:20:5
Don't suppress move errors for union fields
2019-12-15 05:08:43 -06:00
|
LL | *u.c
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 `*u.c` has type `String`, which does not implement the `Copy` trait
Don't suppress move errors for union fields
2019-12-15 05:08:43 -06:00
error[E0507]: cannot move out of `*u.d` which is behind a raw pointer
remove untagged_union feature gate
2022-06-29 21:33:18 -05:00
--> $DIR/move-from-union-field-issue-66500.rs:24:5
Don't suppress move errors for union fields
2019-12-15 05:08:43 -06:00
|
LL | *u.d
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 `*u.d` has type `String`, which does not implement the `Copy` trait
Don't suppress move errors for union fields
2019-12-15 05:08:43 -06:00
error: aborting due to 4 previous errors
For more information about this error, try `rustc --explain E0507`.
Reference in New Issue Copy Permalink