rust/tests/ui/missing-trait-bounds/missing-trait-bound-for-op.rs

//@ run-rustfix

pub fn foo<T>(s: &[T], t: &[T]) {
    let _ = s == t; //~ ERROR binary operation `==` cannot be applied to type `&[T]`
}

fn main() {}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ run-rustfix`
Tweak binop errors * Suggest potentially missing binop trait bound (fix #73416) * Use structured suggestion for dereference in binop 2020-06-23 17:32:06 -07:00
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			`pub fn foo<T>(s: &[T], t: &[T]) {`
			let _ = s == t; //~ ERROR binary operation `==` cannot be applied to type `&[T]`
Tweak binop errors * Suggest potentially missing binop trait bound (fix #73416) * Use structured suggestion for dereference in binop 2020-06-23 17:32:06 -07:00			`}`
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
Tweak binop errors * Suggest potentially missing binop trait bound (fix #73416) * Use structured suggestion for dereference in binop 2020-06-23 17:32:06 -07:00			`fn main() {}`