rust/tests/ui/suggestions/path-display.stderr

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: 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: 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`.
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]: `Path` doesn't implement `std::fmt::Display`
Suggest using `.display()` when trying to print a `Path` 2018-12-13 00:54:27 +00:00			`--> $DIR/path-display.rs:5:20`
			`\|`
			`LL \| println!("{}", path);`
fix rustc_on_implemented `_Self` paths 2021-03-12 10:48:05 +00:00			\| ^^^^ `Path` cannot be formatted with the default formatter; call `.display()` on it
Suggest using `.display()` when trying to print a `Path` 2018-12-13 00:54:27 +00:00			`\|`
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			= help: the trait `std::fmt::Display` is not implemented for `Path`
fix rustc_on_implemented `_Self` paths 2021-03-12 10:48:05 +00:00			= note: call `.display()` or `.to_string_lossy()` to safely print paths, as they may contain non-Unicode data
Mention first and last macro in backtrace 2022-06-21 02:25:52 +00:00			= 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)
Suggest using `.display()` when trying to print a `Path` 2018-12-13 00:54:27 +00:00
Suggest calling .display() on PathBuf too 2022-02-22 00:58:12 +00:00			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: call `.display()` or `.to_string_lossy()` to safely print paths, as they may contain non-Unicode data
Mention first and last macro in backtrace 2022-06-21 02:25:52 +00:00			= 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)
Suggest calling .display() on PathBuf too 2022-02-22 00:58:12 +00:00
			`error: aborting due to 2 previous errors`
Suggest using `.display()` when trying to print a `Path` 2018-12-13 00:54:27 +00:00
			For more information about this error, try `rustc --explain E0277`.