rust/src/test/ui/object-safety/object-safety-associated-consts.object_safe_for_dispatch.stderr

error[E0038]: the trait `Bar` cannot be made into an object
  --> $DIR/object-safety-associated-consts.rs:14:5
   |
LL |     t
   |     ^ the trait `Bar` cannot be made into an object
   |
   = help: consider moving `X` to another trait
note: for a trait to be "object safe" it needs to allow building a vtable to allow the call to be resolvable dynamically; for more information visit <https://doc.rust-lang.org/reference/items/traits.html#object-safety>
  --> $DIR/object-safety-associated-consts.rs:9:11
   |
LL | trait Bar {
   |       --- this trait cannot be made into an object...
LL |     const X: usize;
   |           ^ ...because it contains this associated `const`
   = note: required because of the requirements on the impl of `CoerceUnsized<&dyn Bar>` for `&T`
   = note: required by cast to type `&dyn Bar`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0038`.
RFC 2027: "first draft" of implementation These are a squashed series of commits. 2019-01-08 15:14:04 -06:00			error[E0038]: the trait `Bar` cannot be made into an object
			`--> $DIR/object-safety-associated-consts.rs:14:5`
			`\|`
			`LL \| t`
			\| ^ the trait `Bar` cannot be made into an object
			`\|`
Wording changes to object unsafe trait errors Stemming from the thread at https://twitter.com/indygreg/status/1223279056398929920 2020-01-31 18:47:00 -06:00			= help: consider moving `X` to another trait
Tweak "object unsafe" errors Fix #77598. 2020-10-15 19:23:45 -05:00			`note: for a trait to be "object safe" it needs to allow building a vtable to allow the call to be resolvable dynamically; for more information visit <https://doc.rust-lang.org/reference/items/traits.html#object-safety>`
			`--> $DIR/object-safety-associated-consts.rs:9:11`
			`\|`
			`LL \| trait Bar {`
			`\| --- this trait cannot be made into an object...`
			`LL \| const X: usize;`
			\| ^ ...because it contains this associated `const`
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 of the requirements on the impl of `CoerceUnsized<&dyn Bar>` for `&T`
RFC 2027: "first draft" of implementation These are a squashed series of commits. 2019-01-08 15:14:04 -06:00			= note: required by cast to type `&dyn Bar`

			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0038`.