If equality is hamiş needed for the derived class you güç skip IEquatable but you need to override the CanEqual to prevent it being equal with base classes (unless of course they should be considered equal).
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Other types which implement structural equality/comparability include tuples and anonymous types - which both clearly benefit from the ability to perform comparison based on their structure and content. A question you didn't ask is:
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 as is documented behavior, some reasoning and reflection would also lead you to the same conclusion.
Although I think the gains from derece boxing will be less than the cost for having CanEqual. In that case you should seal your types and you no longer need CanEqual. Sealing also saf some performance benefits.
If two objects compare birli equal, the GetHashCode method for each object must return the same value. However, if two objects do hamiş compare kakım equal, the GetHashCode methods for the two object do not have to C# IStructuralEquatable nedir return different values.
If those objects do not contain equality/hashcode methods that satisfy that contract, you will have to wrap them and provide correct implementations for those methods yourself in the wrapper.
I've noticed these two interfaces, and several associated classes, have been added in .Kupkuru 4. They seem a bit superfluous to me; I've read several blogs about them, but I still yaşama't figure out what sorun they solve that was tricky before .Kemiksiz 4.
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.
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.
This member is an explicit interface member implementation. It can be used only when the Array instance is cast to an IStructuralEquatable interface.
IStructuralEquatable is used with arrays to determine whether the arrays are structurally equal. The StructuralEqualityComparer.Equals method is used for this purpose.
Just look at the default ValueType.Equals(object) code that gets called otherwise. It's an absolute performance killer that introduces boxing, type evaluation and finally falls back on reflection if any of the fields are reference types.
While writing my own immutable ByteArray class that uses a byte array internally, I implemented the IStructuralEquatable interface.