Keep in mind that for this interface to work correctly, the types within the collection or structure must also implement IStructuralEquatable or provide their own structural equality logic.

Now, when we call Equals ourselves it will directly call our new fancy Equals that takes in a ScreenMetrics, which is great.

The following example creates two identical 3-tuple objects whose components consist of three Double values. The value of the second component is Double.NaN. The example then calls the Tuple.Equals method, and it calls the IStructuralEquatable.Equals method three times. The first time, it passes the default equality comparer that is returned by the EqualityComparer.

Default property. The second time, it passes the default equality comparer that is returned by the StructuralComparisons.StructuralEqualityComparer property. The third time, it passes the custom NanComparer object. Kakım the output from the example shows, the first three method calls return true, whereas the fourth call returns false.

Your browser isn’t supported anymore. Update it to get the best YouTube experience and our latest features. Learn more

The following example defines a NanComparer class that implements the IStructuralEquatable interface. It compares two Double or two Single values by using the equality operator. It passes values of any other type to the default equality comparer.

After some more testing I found that any two arrays with the same first element have the same hash. I still think this is strange behavior.

This is very disappointing behaviour from Microsoft; I'm now wondering if I should review the list of cases I've filed and see if other ones I've submitted have been removed...

The reason why you need the IStructuralEquatable is for defining a new way of comparision that would be right for all the objects .

In addition to this awesome blog Frank and I also dicussed all of this awesome in detail on Merge Conflict on episode 111:

Kemiksiz on a certain ortam, I'm compelled to issue the standard warning not to rely on the values of hashcodes or how they are computed, since it is not guaranteed to be the same across updates or platforms.

The contract of Equals differs from that of IStructuralEquatable, in that it indicates whether 2 objects are logically equal.

Is there any yasal justification for content on the web without an explicit licence being freeware? more hot questions

Being able to specify IStructuralEquatable/IStructuralComparable in such cases is actually useful. It would also be inconvenient to pass a TupleComparer or ArrayComparer everywhere you want to apply this type C# IStructuralEquatable Kullanımı of comparison. The two approaches are not mutually exclusive.