bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity
rust/src/test/ui/suggestions/path-display.stderr

16 lines
739 B
Text
Raw Normal View History

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]: `Path` doesn't implement `std::fmt::Display`
Suggest using `.display()` when trying to print a `Path`
2018-12-12 16:54:27 -08:00
--> $DIR/path-display.rs:5:20
|
LL | println!("{}", path);
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
| ^^^^ `Path` cannot be formatted with the default formatter
Suggest using `.display()` when trying to print a `Path`
2018-12-12 16:54:27 -08: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 10:40:56 +03:00
= 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: required because of the requirements on the impl of `std::fmt::Display` for `&Path`
Suggest using `.display()` when trying to print a `Path`
2018-12-12 16:54:27 -08:00
= note: required by `std::fmt::Display::fmt`
rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros.
2019-12-16 15:56:47 +02:00
= note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
Suggest using `.display()` when trying to print a `Path`
2018-12-12 16:54:27 -08:00
error: aborting due to previous error
For more information about this error, try `rustc --explain E0277`.
Copy permalink