rust/src/test/ui/issues/issue-34229.stderr

error[E0277]: can't compare `Comparable` with `Comparable`
  --> $DIR/issue-34229.rs:2:46
   |
LL | #[derive(PartialEq, PartialOrd)] struct Nope(Comparable);
   |                                              ^^^^^^^^^^ no implementation for `Comparable < Comparable` and `Comparable > Comparable`
   |
   = help: the trait `PartialOrd` is not implemented for `Comparable`
   = note: required by `std::cmp::PartialOrd::partial_cmp`
   = note: this error originates in the derive macro `PartialOrd` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
Add test for #34229 2018-10-15 14:17:54 -07:00			error[E0277]: can't compare `Comparable` with `Comparable`
			`--> $DIR/issue-34229.rs:2:46`
			`\|`
			`LL \| #[derive(PartialEq, PartialOrd)] struct Nope(Comparable);`
			\| ^^^^^^^^^^ no implementation for `Comparable < Comparable` and `Comparable > Comparable`
			`\|`
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 `PartialOrd` is not implemented for `Comparable`
Add test for #34229 2018-10-15 14:17:54 -07:00			= note: required by `std::cmp::PartialOrd::partial_cmp`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 14:52:25 -05:00			= note: this error originates in the derive macro `PartialOrd` (in Nightly builds, run with -Z macro-backtrace for more info)
Add test for #34229 2018-10-15 14:17:54 -07:00
./x.py test --bless 2021-02-09 00:00:00 +00:00			`error: aborting due to previous error`
Add test for #34229 2018-10-15 14:17:54 -07:00
			For more information about this error, try `rustc --explain E0277`.