160b1793b2
notes This commit extends the `#[diagnostic::on_unimplemented]` (and `#[rustc_on_unimplemented]`) attributes to allow multiple `note` options. This enables emitting multiple notes for custom error messages. For now I've opted to not change any of the existing usages of `#[rustc_on_unimplemented]` and just updated the relevant compile tests.
26 lines
1.5 KiB
Plaintext
26 lines
1.5 KiB
Plaintext
error[E0277]: `Path` doesn't implement `std::fmt::Display`
|
|
--> $DIR/path-display.rs:5:20
|
|
|
|
|
LL | println!("{}", path);
|
|
| ^^^^ `Path` cannot be formatted with the default formatter; call `.display()` on it
|
|
|
|
|
= help: the trait `std::fmt::Display` is not implemented for `Path`
|
|
= note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead
|
|
= note: call `.display()` or `.to_string_lossy()` to safely print paths, as they may contain non-Unicode data
|
|
= note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error[E0277]: `PathBuf` doesn't implement `std::fmt::Display`
|
|
--> $DIR/path-display.rs:9:20
|
|
|
|
|
LL | println!("{}", path);
|
|
| ^^^^ `PathBuf` cannot be formatted with the default formatter; call `.display()` on it
|
|
|
|
|
= help: the trait `std::fmt::Display` is not implemented for `PathBuf`
|
|
= note: in format strings you may be able to use `{:?}` (or {:#?} for pretty-print) instead
|
|
= note: call `.display()` or `.to_string_lossy()` to safely print paths, as they may contain non-Unicode data
|
|
= note: this error originates in the macro `$crate::format_args_nl` which comes from the expansion of the macro `println` (in Nightly builds, run with -Z macro-backtrace for more info)
|
|
|
|
error: aborting due to 2 previous errors
|
|
|
|
For more information about this error, try `rustc --explain E0277`.
|