nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2025-01-09 14:25:24 +00:00
Code Issues Packages Projects Releases Wiki Activity
9832374f6e
rust/src/test/ui/wf/wf-convert-unsafe-trait-obj-box.stderr

46 lines
1.8 KiB
Plaintext
Raw Normal View History

RFC 2027: "first draft" of implementation These are a squashed series of commits.
2019-01-08 21:14:04 +00:00
error[E0038]: the trait `Trait` cannot be made into an object
--> $DIR/wf-convert-unsafe-trait-obj-box.rs:16:33
|
Point at `Sized` bound
2020-01-19 22:53:37 +00:00
LL | trait Trait: Sized {}
Wording changes to object unsafe trait errors Stemming from the thread at https://twitter.com/indygreg/status/1223279056398929920
2020-02-01 00:47:00 +00:00
| ----- ----- ...because it requires `Self: Sized`
| |
| this trait cannot be made into an object...
Point at `Sized` bound
2020-01-19 22:53:37 +00:00
...
RFC 2027: "first draft" of implementation These are a squashed series of commits.
2019-01-08 21:14:04 +00:00
LL | let t_box: Box<dyn Trait> = Box::new(S);
| ^^^^^^^^^^^ the trait `Trait` cannot be made into an object
|
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
= note: required because of the requirements on the impl of `CoerceUnsized<Box<dyn Trait>>` for `Box<S>`
= note: required by cast to type `Box<dyn Trait>`
RFC 2027: "first draft" of implementation These are a squashed series of commits.
2019-01-08 21:14:04 +00:00
error[E0038]: the trait `Trait` cannot be made into an object
--> $DIR/wf-convert-unsafe-trait-obj-box.rs:17:15
|
Point at `Sized` bound
2020-01-19 22:53:37 +00:00
LL | trait Trait: Sized {}
Wording changes to object unsafe trait errors Stemming from the thread at https://twitter.com/indygreg/status/1223279056398929920
2020-02-01 00:47:00 +00:00
| ----- ----- ...because it requires `Self: Sized`
| |
| this trait cannot be made into an object...
Point at `Sized` bound
2020-01-19 22:53:37 +00:00
...
RFC 2027: "first draft" of implementation These are a squashed series of commits.
2019-01-08 21:14:04 +00:00
LL | takes_box(Box::new(S));
| ^^^^^^^^^^^ the trait `Trait` cannot be made into an object
|
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
= note: required because of the requirements on the impl of `CoerceUnsized<Box<dyn Trait>>` for `Box<S>`
= note: required by cast to type `Box<(dyn Trait + 'static)>`
RFC 2027: "first draft" of implementation These are a squashed series of commits.
2019-01-08 21:14:04 +00:00
error[E0038]: the trait `Trait` cannot be made into an object
--> $DIR/wf-convert-unsafe-trait-obj-box.rs:15:5
|
Point at `Sized` bound
2020-01-19 22:53:37 +00:00
LL | trait Trait: Sized {}
Wording changes to object unsafe trait errors Stemming from the thread at https://twitter.com/indygreg/status/1223279056398929920
2020-02-01 00:47:00 +00:00
| ----- ----- ...because it requires `Self: Sized`
| |
| this trait cannot be made into an object...
Point at `Sized` bound
2020-01-19 22:53:37 +00:00
...
RFC 2027: "first draft" of implementation These are a squashed series of commits.
2019-01-08 21:14:04 +00:00
LL | Box::new(S) as Box<dyn Trait>;
| ^^^^^^^^^^^ the trait `Trait` cannot be made into an object
|
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
= note: required because of the requirements on the impl of `CoerceUnsized<Box<dyn Trait>>` for `Box<S>`
= note: required by cast to type `Box<dyn Trait>`
RFC 2027: "first draft" of implementation These are a squashed series of commits.
2019-01-08 21:14:04 +00:00
error: aborting due to 3 previous errors
For more information about this error, try `rustc --explain E0038`.
Reference in New Issue Copy Permalink