Re: Top 10 Worst C# Features

[Ben Bacarisse <ben.usenet@bsb.me.uk>]

Stefan.Lucks@uni-weimar.de writes:

> On Wed, 14 Oct 2015, Paul Rubin wrote:
>
>> Ben Bacarisse <ben.usenet@bsb.me.uk> writes:
>>> Do you mean that there are reasons to permit !(a == b) and a != b to
>>> have different values in some cases?
>>
>> I think he meant they should both return the same value, but it is ok if
>> they don't use the same algorithm.  Of course it may be possible for the
>> compiler to optimize the first into the second.  The idea is just that
>> if (a != b) { ... }   can be much faster than  if (a == b) { ... } .
>
> As I seem to understand, Ben questioned that either the test on
> equality or on non-equality could be much faster than the other one.

Yes, exactly.  If !(a == b) and a != b don't have to be the same for
this imagined type then of course one can be faster than the other, but
if the usual laws are to hold, implementing one can't be anything but
trivially easier then the other.

<snip>
-- 
Ben.