The C# compiler requires that whenever a custom type defines operator ==, it must also define != (see here).
==
!=
Why?
I\'m curious to k
Probably just something they didn't think of of didn't have time to do.
I always use your method when I overload ==. Then I just use it in the other one.
You're right, with a small amount of work, the compiler could give this to us for free.