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?
Now, when we call Equals ourselves it will directly call our new fancy Equals that takes in a ScreenMetrics, which is great.
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:
Do derece fear because if you simply implement IEquatable the dictionary will use the strongly typed version! The nice thing is that we kind of actually already did this! So now we just have to do this:
It is used by the third example as an argument to the Equals(Object, IEqualityComparer) method of the IStructuralEquatable interface that tuples implement. 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.
If two objects compare kakım equal, the GetHashCode method for each object must return the same value. However, if two objects do not compare bey equal, the GetHashCode methods for the two object do hamiş have to return different values.
The IEquatable implementation will require one less cast for these classes and as a result will be slightly faster than the standard object.Equals method that would be used otherwise. As an example see the different implementation of the two methods:
When an implementer overrides the virtual Equals method in a struct, the purpose is to provide a more efficient means of performing the value equality check and optionally to base the comparison on some subset of the struct's field or properties.
The first issue we see here is that this struct is mutable in that you dirilik actually change the data later on via the kaş properties. C# IStructuralEquatable Temel Özellikleri There was no real reason that we introduced this except that we were used to it.
Konstrüktif eşitlik, müsavi değerlere malik oldukları karınin dü nesnenin hemayar evetğu mazmunına hasılat. Aynı fiziksel nesneye başvurdıkları muhtevain iki nesne saksıvurusunun bedel olduğunu gösteren referans eşitliğinden değişikdır. arabirimi, IStructuralEquatable koleksiyon nesnelerinin yapısal eşitliğini denetlemek muhtevain özelleştirilmiş katlaştırmalar uygulamanıza imkân tanılamar.
Amma velakin bu yapımız class denli kompleks aksiyonlemler yürekin tasarlanmış bir yapı gerektirmiyorsa ve tutulacak verileri enkapsüle geçirmek yetiyorsa işte bu ezgi durumlarda struct yapkaloriı yeğleme edebiliriz.
IStructuralEquatable is used with arrays to determine whether the arrays are structurally equal. The StructuralEqualityComparer.Equals method is used for this purpose.
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.
While writing my own immutable ByteArray class that uses a byte array internally, I implemented the IStructuralEquatable interface.