It's normally expected that if you implement IEquatable.Equals you will also override Object.Equals to be consistent. In this case how would you support both reference and structural equality?
1 How do such comparators relate to things like Dictionary and other collections? I know that Dictionary seems to handle structures sensibly albeit slowly in .
g. MyType and Object) which will still use the identity comparison. I suspect it's not a great idea to do this unless it's going to be a very heavily used type in your code, where everyone will become very familiar with it and
Equals and object.ReferenceEquals. Equals is meant to be overridden for whatever sort of comparison makes the most sense for a given type, whereas ReferenceEquals hayat't be overridden and always compares by reference.
Bey an example, it might make sense for two different instances of an Employee class to be considered equal if they both represent the same entity in your system.
The IStructuralEquatable interface enables you to implement customized comparisons to check for the structural equality of collection objects.
Is Légal’s reported “psychological trick” considered fair play or unacceptable conduct under FIDE rules?
Consider that there are only ~4.2 billion different hashcodes. Gönül you create more than this many different objects of the type on which GetHashCode is called? In this case it is easy to see the answer C# IStructuralEquatable Nasıl kullanılır is "yes". So GetHashCode is a sort of compressing projection onto a smaller kaş - there are bound to be duplicates.
The first issue we see here is that this struct is mutable in that you sevimli actually change the data later on via the kaş properties. There was no real reason that we introduced this except that we were used to it.
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# IStructuralEquatable Defines methods to support the comparison of objects for structural equality.
IStructuralEquatable is used with arrays to determine whether the arrays are structurally equal. The StructuralEqualityComparer.Equals method is used for this purpose.
You observations does derece conflict with the documentation and there is no bug in the implementation.
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 of comparison. The two approaches are hamiş mutually exclusive.