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.
Bu tür bir karşılaştırma, makale saksılıklarının sıralamasının önemli başüstüneğu durumlarda, strüktürel benzerliklerin veya farklılıkların belirlenmesine yardımcı mümkün.
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.
As far as I see this is only exposed through the StructuralComparisons class. The only way I kişi figure out to make this useful is to make a StructuralEqualityComparer helper class bey follow:
This code technically works, but is sort of a hot mess and is derece really maintainable. Anyone using the library would have to write this code kakım well. The next logical step would be to just use .Equals on the entire metrics.
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 derece trigger new events unless a value changed a whole new world opened up to me.
So, I am apparently wrong bey unequal objects may have equal hash codes. But isn't GetHashCode returning a somewhat randomly distributed kaş of values a requirement?
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.
Fantasy TV series with a male protagonist who uses a bow and arrows and has C# IStructuralEquatable nedir a hawk/falcon/eagle type bird companion
If you read this entire post and are thinking wow that is a lot of code and steps to remember then do not fear because Dustin told me and showed me that Visual Studio will generate all of this for you!!!!! Check this out:
To achieve this, employee objects with matching SSN properties would be treated kakım logically equal, even if they were derece structurally equal. Share Improve this answer Follow
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 of comparison. The two approaches are derece mutually exclusive.