rust/tests/ui/suggestions/invalid-bin-op.stderr

error[E0369]: binary operation `==` cannot be applied to type `S<T>`
  --> $DIR/invalid-bin-op.rs:2:15
   |
LL |     let _ = s == t;
   |             - ^^ - S<T>
   |             |
   |             S<T>
   |
note: an implementation of `PartialEq<_>` might be missing for `S<T>`
  --> $DIR/invalid-bin-op.rs:5:1
   |
LL | struct S<T>(T);
   | ^^^^^^^^^^^ must implement `PartialEq<_>`
help: consider annotating `S<T>` with `#[derive(PartialEq)]`
   |
LL | #[derive(PartialEq)]
   |
help: consider introducing a `where` clause, but there might be an alternative better way to express this requirement
   |
LL | pub fn foo<T>(s: S<T>, t: S<T>) where S<T>: PartialEq {
   |                                 +++++++++++++++++++++

error: aborting due to previous error

For more information about this error, try `rustc --explain E0369`.
Suggest type param trait bound for binop only when appropriate Verify that the binop trait is implemented for the types if all the involved type parameters are replaced with fresh inferred types. When this is the case, it means that the type parameter was indeed missing a trait bound. If this is not the case, provide a generic `note` refering to the type that doesn't implement the expected trait. 2020-06-24 16:17:04 -07:00			error[E0369]: binary operation `==` cannot be applied to type `S<T>`
			`--> $DIR/invalid-bin-op.rs:2:15`
			`\|`
			`LL \| let _ = s == t;`
			`\| - ^^ - S<T>`
			`\| \|`
			`\| S<T>`
			`\|`
Consider unfulfilled obligations in binop errors When encountering a binop where the types would have been accepted, if all the predicates had been fulfilled, include information about the predicates and suggest appropriate `#[derive]`s if possible. Point at trait(s) that needs to be `impl`emented. 2021-09-28 14:48:54 +00:00			note: an implementation of `PartialEq<_>` might be missing for `S<T>`
			`--> $DIR/invalid-bin-op.rs:5:1`
			`\|`
			`LL \| struct S<T>(T);`
Shorten def_span for more items. 2022-02-13 16:27:59 +01:00			\| ^^^^^^^^^^^ must implement `PartialEq<_>`
Consider unfulfilled obligations in binop errors When encountering a binop where the types would have been accepted, if all the predicates had been fulfilled, include information about the predicates and suggest appropriate `#[derive]`s if possible. Point at trait(s) that needs to be `impl`emented. 2021-09-28 14:48:54 +00:00			help: consider annotating `S<T>` with `#[derive(PartialEq)]`
			`\|`
			`LL \| #[derive(PartialEq)]`
			`\|`
Handle empty where-clause better 2022-06-05 17:37:45 -07:00			help: consider introducing a `where` clause, but there might be an alternative better way to express this requirement
Replace suggest_constraining_param with suggest_restricting_param_bound to fix incorrect suggestion for trait bounds involving binary operators. Fixes #93927, #92347, #93744. 2022-02-15 14:49:16 -08:00			`\|`
			`LL \| pub fn foo<T>(s: S<T>, t: S<T>) where S<T>: PartialEq {`
			`\| +++++++++++++++++++++`
Suggest type param trait bound for binop only when appropriate Verify that the binop trait is implemented for the types if all the involved type parameters are replaced with fresh inferred types. When this is the case, it means that the type parameter was indeed missing a trait bound. If this is not the case, provide a generic `note` refering to the type that doesn't implement the expected trait. 2020-06-24 16:17:04 -07:00
			`error: aborting due to previous error`

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