rust/src/test/ui/derives/derives-span-Eq-tuple-struct.stderr

error[E0277]: the trait bound `Error: Eq` is not satisfied
  --> $DIR/derives-span-Eq-tuple-struct.rs:8:5
   |
LL |     Error
   |     ^^^^^ the trait `Eq` is not implemented for `Error`
   | 
  ::: $SRC_DIR/core/src/cmp.rs:LL:COL
   |
LL | pub struct AssertParamIsEq<T: Eq + ?Sized> {
   |                               -- required by this bound in `AssertParamIsEq`
   |
   = note: this error originates in the derive macro `Eq` (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`.
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 02:40:56 -05:00			error[E0277]: the trait bound `Error: Eq` is not satisfied
tests: remove ignore directives from tests that mention core/alloc/std spans. 2020-03-31 20:10:13 -05:00			`--> $DIR/derives-span-Eq-tuple-struct.rs:8:5`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| Error`
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 02:40:56 -05:00			\| ^^^^^ the trait `Eq` is not implemented for `Error`
Use `PredicateObligation`s instead of `Predicate`s Keep more information about trait binding failures. 2020-03-03 17:07:04 -06:00			`\|`
mv std libs to library/ 2020-06-11 21:31:49 -05:00			`::: $SRC_DIR/core/src/cmp.rs:LL:COL`
Use `PredicateObligation`s instead of `Predicate`s Keep more information about trait binding failures. 2020-03-03 17:07:04 -06:00			`\|`
			`LL \| pub struct AssertParamIsEq<T: Eq + ?Sized> {`
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 02:40:56 -05:00			\| -- required by this bound in `AssertParamIsEq`
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00			`\|`
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 13:52:25 -06:00			= note: this error originates in the derive macro `Eq` (in Nightly builds, run with -Z macro-backtrace for more info)
Moved compile-fail tests to ui tests. 2018-08-08 07:28:26 -05:00
			`error: aborting due to previous error`

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