suspicious_arithmetic_impl and OpAssign

[l0calh05t]

While the suspicious_arithmetic_impl is a bit overeager itself (see #3215), it also fails to detect the type of mistake it is supposed to detect when an Op-trait is implemented in terms of the corresponding OpAssign-trait. In the example below, Add has "accidentally" been implemented in terms of *=/MulAssign, but clippy 0.0.212 (4ee1206 2020-02-01) does not issue a warning:

#[derive(Clone, Debug)]
struct Foo(f32);

impl std::ops::Mul<&Foo> for &Foo {
	type Output = Foo;
	fn mul(self, other: &Foo) -> Foo {
		let mut ret = self.clone();
		ret.0 *= other.0;
		ret
	}
}

impl std::ops::Add<&Foo> for &Foo {
	type Output = Foo;
	fn add(self, other: &Foo) -> Foo {
		let mut ret = self.clone();
		ret.0 *= other.0; // oops, but no warning
		ret
	}
}

fn main() {
	println!("{:?}", &Foo(2.0) * &Foo(3.0));
	println!("{:?}", &Foo(2.0) + &Foo(3.0));
}

[ThibsG]

This lint seems to be correctly triggered or am I missing something?
Playground

[l0calh05t]

@ThibsG Doesn't trigger on your playground link either. Tried both debug and release and stable and nightly.

[ThibsG]

But if you do "Tools" then "Clippy" it triggers right?

[l0calh05t]

It does, yes. Oddly, it does for me locally now too... closing for now.