Proposal: add a context for RHS of equality operations. about language

[lrhn]

Agree.
We do allow overriding operator==, so we should also use the overridden type in the minuscule amount of cases where someone does that. (But… like why? And like don't!)

The other alternative is to remove coercion as well, but this is a statically decided behavior, so it's cost-free in most cases (because K? will be Object? in almost every case), and in the hypothetical case where we know that calling is going to throw if we don't coerce, we might as well do the consistent thing.

(We still can't change the return type to the declared return type, even if we can now have extension types as subtypes of bool. Unless Erik's proposal of allowing extension type return types for fx async functions can be extended to operator==.)