https://issues.dlang.org/show_bug.cgi?id=17245
Vladimir Panteleev <dlang-bugzi...@thecybershadow.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dlang-bugzilla@thecybershad
| |ow.net
--- Comment #2 from Vladimir Panteleev <dlang-bugzi...@thecybershadow.net> ---
(In reply to Jack Stouffer from comment #0)
> Here, the compiler can be helpful by outputing an error if the used opEquals
> is marked as pure. There's no way that a pure opEquals should be used in an
> expression with no effect.
A pure opEquals doesn't seem to generate a warning/error either:
struct S
{
bool opEquals(ref const S s) pure { return false; }
}
void fun()
{
S a, b;
a == b;
}
--
