rust/tests/ui/issues/issue-21596.stderr

error[E0599]: `*const u8` doesn't implement `std::fmt::Display`
  --> $DIR/issue-21596.rs:4:22
   |
LL |     println!("{}", z.to_string());
   |                      ^^^^^^^^^ `*const u8` cannot be formatted with the default formatter
   |
   = note: try using `<*const T>::as_ref()` to get a reference to the type behind the pointer: https://doc.rust-lang.org/std/primitive.pointer.html#method.as_ref
   = note: using `<*const T>::as_ref()` on a pointer which is unaligned or points to invalid or uninitialized memory is undefined behavior
   = note: the following trait bounds were not satisfied:
           `*const u8: std::fmt::Display`
           which is required by `*const u8: ToString`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0599`.
diagnostics: use rustc_on_unimplemented to recommend `[].iter()` To make this work, the `#[rustc_on_unimplemented]` data needs to be used to report method resolution errors, which is most of what this commit does. Fixes #94581 2022-03-08 11:04:20 -07:00			error[E0599]: `*const u8` doesn't implement `std::fmt::Display`
Suggest using `as_ref` on `*const T` 2019-06-01 16:24:19 -07:00			`--> $DIR/issue-21596.rs:4:22`
			`\|`
			`LL \| println!("{}", z.to_string());`
diagnostics: use rustc_on_unimplemented to recommend `[].iter()` To make this work, the `#[rustc_on_unimplemented]` data needs to be used to report method resolution errors, which is most of what this commit does. Fixes #94581 2022-03-08 11:04:20 -07:00			\| ^^^^^^^^^ `*const u8` cannot be formatted with the default formatter
Suggest using `as_ref` on `*const T` 2019-06-01 16:24:19 -07:00			`\|`
			= note: try using `<*const T>::as_ref()` to get a reference to the type behind the pointer: https://doc.rust-lang.org/std/primitive.pointer.html#method.as_ref
Add info about undefined behavior to as_ref suggestions 2019-07-14 15:05:25 -04:00			= note: using `<*const T>::as_ref()` on a pointer which is unaligned or points to invalid or uninitialized memory is undefined behavior
Avoid describing a method as 'not found' when bounds are unsatisfied Fixes #76267 When there is a single applicable method candidate, but its trait bounds are not satisfied, we avoid saying that the method is "not found". Insted, we update the error message to directly mention which bounds are not satisfied, rather than mentioning them in a note. 2020-09-26 17:20:14 -04:00			`= note: the following trait bounds were not satisfied:`
Review comments: split requirement text to multiple lines for readability 2020-02-21 13:39:47 -08:00			`*const u8: std::fmt::Display`
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			which is required by `*const u8: ToString`
Suggest using `as_ref` on `*const T` 2019-06-01 16:24:19 -07:00
			`error: aborting due to previous error`

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