rust/tests/ui/suggestions/issue-71394-no-from-impl.stderr

error[E0277]: the trait bound `&[i8]: From<&[u8]>` is not satisfied
  --> $DIR/issue-71394-no-from-impl.rs:8:25
   |
LL |     let _: &[i8] = data.into();
   |                         ^^^^ the trait `From<&[u8]>` is not implemented for `&[i8]`
   |
   = help: the following other types implement trait `From<T>`:
             <[bool; LANES] as From<Mask<T, LANES>>>
             <[T; N] as From<Simd<T, N>>>
             <[T; 1] as From<(T,)>>
             <[T; 2] as From<(T, T)>>
             <[T; 3] as From<(T, T, T)>>
             <[T; 4] as From<(T, T, T, T)>>
             <[T; 5] as From<(T, T, T, T, T)>>
             <[T; 6] as From<(T, T, T, T, T, T)>>
           and 6 others
   = note: required for `&[u8]` to implement `Into<&[i8]>`

error: aborting due to 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 10:40:56 +03:00			error[E0277]: the trait bound `&[i8]: From<&[u8]>` is not satisfied
Bump version of object and related crates 2023-02-01 12:29:19 +08:00			`--> $DIR/issue-71394-no-from-impl.rs:8:25`
Add regression test for #71394 2020-04-27 12:34:00 -07:00			`\|`
			`LL \| let _: &[i8] = data.into();`
Point at method call when it is the source of the bound error 2022-12-11 14:49:50 -08:00			\| ^^^^ the trait `From<&[u8]>` is not implemented for `&[i8]`
Add regression test for #71394 2020-04-27 12:34:00 -07:00			`\|`
Refer to the TraitRef::identity in the message to be clearer 2022-03-27 02:02:07 +00:00			= help: the following other types implement trait `From<T>`:
Don't sort strings right after we just sorted by types 2023-06-27 23:31:06 +00:00			`<[bool; LANES] as From<Mask<T, LANES>>>`
			`<[T; N] as From<Simd<T, N>>>`
--bless tests 2022-06-02 13:14:43 +04:00			`<[T; 1] as From<(T,)>>`
			`<[T; 2] as From<(T, T)>>`
			`<[T; 3] as From<(T, T, T)>>`
			`<[T; 4] as From<(T, T, T, T)>>`
Don't sort strings right after we just sorted by types 2023-06-27 23:31:06 +00:00			`<[T; 5] as From<(T, T, T, T, T)>>`
			`<[T; 6] as From<(T, T, T, T, T, T)>>`
fix the error check 2023-08-15 00:57:18 +08:00			`and 6 others`
Reword "Required because of the requirements on the impl of ..." 2022-08-15 21:31:37 +01:00			= note: required for `&[u8]` to implement `Into<&[i8]>`
Add regression test for #71394 2020-04-27 12:34:00 -07:00
			`error: aborting due to previous error`

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