rust/tests/ui/traits/issue-71036.stderr

error[E0277]: the trait bound `&'a T: Unsize<&'a U>` is not satisfied
  --> $DIR/issue-71036.rs:11:1
   |
LL | impl<'a, T: ?Sized + Unsize<U>, U: ?Sized> DispatchFromDyn<Foo<'a, U>> for Foo<'a, T> {}
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `Unsize<&'a U>` is not implemented for `&'a T`, which is required by `&'a &'a T: DispatchFromDyn<&'a &'a U>`
   |
   = note: all implementations of `Unsize` are provided automatically by the compiler, see <https://doc.rust-lang.org/stable/std/marker/trait.Unsize.html> for more information
   = note: required for `&'a &'a T` to implement `DispatchFromDyn<&'a &'a U>`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0277`.
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			error[E0277]: the trait bound `&'a T: Unsize<&'a U>` is not satisfied
Don't ICE on missing `Unsize` impl 2020-05-14 10:37:58 +00:00			`--> $DIR/issue-71036.rs:11:1`
			`\|`
			`LL \| impl<'a, T: ?Sized + Unsize<U>, U: ?Sized> DispatchFromDyn<Foo<'a, U>> for Foo<'a, T> {}`
Provide more context on derived obligation error primary label Expand the primary span of E0277 when the immediate unmet bound is not what the user wrote: ``` error[E0277]: the trait bound `i32: Bar` is not satisfied --> f100.rs:6:6 \| 6 \| <i32 as Foo>::foo(); \| ^^^ the trait `Bar` is not implemented for `i32`, which is required by `i32: Foo` \| help: this trait has no implementations, consider adding one --> f100.rs:2:1 \| 2 \| trait Bar {} \| ^^^^^^^^^ note: required for `i32` to implement `Foo` --> f100.rs:3:14 \| 3 \| impl<T: Bar> Foo for T {} \| --- ^^^ ^ \| \| \| unsatisfied trait bound introduced here ``` Fix #40120. 2024-01-29 18:31:02 +00:00			\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `Unsize<&'a U>` is not implemented for `&'a T`, which is required by `&'a &'a T: DispatchFromDyn<&'a &'a U>`
Don't ICE on missing `Unsize` impl 2020-05-14 10:37:58 +00:00			`\|`
			= note: all implementations of `Unsize` are provided automatically by the compiler, see <https://doc.rust-lang.org/stable/std/marker/trait.Unsize.html> for more information
Reword "Required because of the requirements on the impl of ..." 2022-08-15 20:31:37 +00:00			= note: required for `&'a &'a T` to implement `DispatchFromDyn<&'a &'a U>`
Don't ICE on missing `Unsize` impl 2020-05-14 10:37:58 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Don't ICE on missing `Unsize` impl 2020-05-14 10:37:58 +00:00
			For more information about this error, try `rustc --explain E0277`.