However, this is an implementation detail and unless you want to rely on this in your code you cannot create a stable hash code provide an object that implements IStructuralEquatable.
Important Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
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.
Daniel A.A. PelsmaekerDaniel A.A. Pelsmaeker 49.2k2121 gold badges112112 silver badges160160 bronze badges 5 In addition to answers which point to duplicate hashcodes bey is documented behavior, some reasoning and reflection would also lead you to the same conclusion.
I'm amazed that the most important reason is hamiş mentioned here. IEquatable was introduced mainly for structs for two reasons:
I never put much thought into using a struct over a class or even additional optimizations because to me the struct was optimized already. When I was working on fixing a bug in our DeviceDisplay to not trigger new events unless a value changed a whole new world opened up to me.
1 My understanding is that it's used for collection like types, and encapsulates the structural part of the comparison, but leaved the comparison of the elements to a comparer passed in by the C# IStructuralEquatable nedir user. But I'm hamiş really sure if I really got it.
Defines a generalized method that a value type or class implements to create a type-specific method for determining equality of instances.
(doesn't violate documentation), but it is clearly hamiş bey good birli it would be if 0 were replaced with i. Also there's no reason to loop if the code were just going to use a single value from the array.
In all my years of development and blogging I never thought I would be writing about how amazing a C# struct is, how awesome IEquatable is, and how C# 7 features make implementing all of it mind blowing.
C# IStructuralComparable Determines whether the current collection object precedes, occurs in the same position birli, or follows another object in the sort order.
Defines methods to support the comparison of objects for structural equality. Structural equality means that two objects are equal because they have equal values.
The IStructuralEquatable interface supports only custom comparisons for structural equality. The IStructuralComparable interface supports custom structural comparisons for sorting and ordering.
While writing my own immutable ByteArray class that uses a byte array internally, I implemented the IStructuralEquatable interface.