mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
4d55affc12
rust/tests/ui/fmt/send-sync.stderr

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

44 lines
1.9 KiB
Plaintext
Raw Normal View History

Move to using an extern type for opaqueness This prevents accidental dereferences and so forth of the Void type, as well as cleaning up the error message to reference Opaque rather than the more complicated PhantomData type.
2020-02-15 17:47:34 -06:00
error[E0277]: `core::fmt::Opaque` cannot be shared between threads safely
Rework point-at-arg
2022-08-16 01:27:22 -05:00
--> $DIR/send-sync.rs:8:10
Prevent fmt::Arguments from being shared across threads Fixes #45197
2017-10-11 03:57:30 -05:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | send(format_args!("{:?}", c));
Rework point-at-arg
2022-08-16 01:27:22 -05:00
| ---- ^^^^^^^^^^^^^^^^^^^^^^^ `core::fmt::Opaque` cannot be shared between threads safely
| |
| required by a bound introduced by this call
Prevent fmt::Arguments from being shared across threads Fixes #45197
2017-10-11 03:57:30 -05:00
|
Update tests.
2022-09-08 05:45:17 -05:00
= help: within `[core::fmt::ArgumentV1<'_>]`, the trait `Sync` is not implemented for `core::fmt::Opaque`
Move to using an extern type for opaqueness This prevents accidental dereferences and so forth of the Void type, as well as cleaning up the error message to reference Opaque rather than the more complicated PhantomData type.
2020-02-15 17:47:34 -06:00
= note: required because it appears within the type `&core::fmt::Opaque`
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: required because it appears within the type `ArgumentV1<'_>`
= note: required because it appears within the type `[ArgumentV1<'_>]`
Update tests.
2022-09-08 05:45:17 -05:00
= note: required for `&[core::fmt::ArgumentV1<'_>]` to implement `Send`
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: required because it appears within the type `Arguments<'_>`
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
note: required by a bound in `send`
--> $DIR/send-sync.rs:1:12
|
LL | fn send<T: Send>(_: T) {}
| ^^^^ required by this bound in `send`
Prevent fmt::Arguments from being shared across threads Fixes #45197
2017-10-11 03:57:30 -05:00
Move to using an extern type for opaqueness This prevents accidental dereferences and so forth of the Void type, as well as cleaning up the error message to reference Opaque rather than the more complicated PhantomData type.
2020-02-15 17:47:34 -06:00
error[E0277]: `core::fmt::Opaque` cannot be shared between threads safely
Rework point-at-arg
2022-08-16 01:27:22 -05:00
--> $DIR/send-sync.rs:9:10
Prevent fmt::Arguments from being shared across threads Fixes #45197
2017-10-11 03:57:30 -05:00
|
Update tests
2019-03-09 06:03:44 -06:00
LL | sync(format_args!("{:?}", c));
Rework point-at-arg
2022-08-16 01:27:22 -05:00
| ---- ^^^^^^^^^^^^^^^^^^^^^^^ `core::fmt::Opaque` cannot be shared between threads safely
| |
| required by a bound introduced by this call
Prevent fmt::Arguments from being shared across threads Fixes #45197
2017-10-11 03:57:30 -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
= help: within `Arguments<'_>`, the trait `Sync` is not implemented for `core::fmt::Opaque`
Move to using an extern type for opaqueness This prevents accidental dereferences and so forth of the Void type, as well as cleaning up the error message to reference Opaque rather than the more complicated PhantomData type.
2020-02-15 17:47:34 -06:00
= note: required because it appears within the type `&core::fmt::Opaque`
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: required because it appears within the type `ArgumentV1<'_>`
= note: required because it appears within the type `[ArgumentV1<'_>]`
= note: required because it appears within the type `&[ArgumentV1<'_>]`
= note: required because it appears within the type `Arguments<'_>`
Use note to point at bound introducing requirement
2021-07-31 11:26:55 -05:00
note: required by a bound in `sync`
--> $DIR/send-sync.rs:2:12
|
LL | fn sync<T: Sync>(_: T) {}
| ^^^^ required by this bound in `sync`
Prevent fmt::Arguments from being shared across threads Fixes #45197
2017-10-11 03:57:30 -05:00
error: aborting due to 2 previous errors
update tests
2018-03-03 08:59:40 -06:00
For more information about this error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink