rust/tests/ui/where-clauses/where-clauses-method-unsati...

error[E0277]: the trait bound `Bar: Eq` is not satisfied
  --> $DIR/where-clauses-method-unsatisfied.rs:18:7
   |
LL |     x.equals(&x);
   |       ^^^^^^ the trait `Eq` is not implemented for `Bar`
   |
note: required by a bound in `Foo::<T>::equals`
  --> $DIR/where-clauses-method-unsatisfied.rs:11:52
   |
LL |     fn equals(&self, u: &Foo<T>) -> bool where T : Eq {
   |                                                    ^^ required by this bound in `Foo::<T>::equals`
help: consider annotating `Bar` with `#[derive(Eq)]`
   |
LL + #[derive(Eq)]
LL | struct Bar; // does not implement Eq
   |

error: aborting due to 1 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 15:40:56 +08:00			error[E0277]: the trait bound `Bar: Eq` is not satisfied
Rework point-at-arg 2022-08-16 14:27:22 +08:00			`--> $DIR/where-clauses-method-unsatisfied.rs:18:7`
Moved compile-fail tests to ui tests. 2018-08-08 20:28:26 +08:00			`\|`
			`LL \| x.equals(&x);`
Rework point-at-arg 2022-08-16 14:27:22 +08:00			\| ^^^^^^ the trait `Eq` is not implemented for `Bar`
Point at source of trait bound obligations in more places Be more thorough in using `ItemObligation` and `BindingObligation` when evaluating obligations so that we can point at trait bounds that introduced unfulfilled obligations. We no longer incorrectly point at unrelated trait bounds (`substs-ppaux.verbose.stderr`). In particular, we now point at trait bounds on method calls. We no longer point at "obvious" obligation sources (we no longer have a note pointing at `Trait` saying "required by a bound in `Trait`", like in `associated-types-no-suitable-supertrait*`). Address part of #89418. 2021-10-06 07:04:09 +08:00			`\|`
			note: required by a bound in `Foo::<T>::equals`
			`--> $DIR/where-clauses-method-unsatisfied.rs:11:52`
			`\|`
			`LL \| fn equals(&self, u: &Foo<T>) -> bool where T : Eq {`
			\| ^^ required by this bound in `Foo::<T>::equals`
Suggest derivable trait on E0277 2022-03-31 22:58:45 +08:00			help: consider annotating `Bar` with `#[derive(Eq)]`
			`\|`
Tweak output for 'add line' suggestion 2023-03-18 10:18:39 +08:00			`LL + #[derive(Eq)]`
			`LL \| struct Bar; // does not implement Eq`
Suggest derivable trait on E0277 2022-03-31 22:58:45 +08:00			`\|`
Moved compile-fail tests to ui tests. 2018-08-08 20:28:26 +08:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 23:44:16 +08:00			`error: aborting due to 1 previous error`
Moved compile-fail tests to ui tests. 2018-08-08 20:28:26 +08:00
			For more information about this error, try `rustc --explain E0277`.