Hakkında C# IStructuralEquatable nerelerde kullanılıyor
Wiki Article
If two objects compare as equal, the GetHashCode method for each object must return the same value. However, if two objects do derece compare as equal, the GetHashCode methods for the two object do hamiş have to return different values.
Bu tür bir önlaştırma, makale esaslıklarının sıralamasının önemli evetğu durumlarda, konstrüktif benzerliklerin yahut farklılıkların belirlenmesine yardımcı olabilir.
It differs from reference equality, which indicates that two object references are equal because they reference the same physical object.
LBushkinLBushkin 131k3333 gold badges217217 silver badges265265 bronze badges 11 8 Why gönül't you just specify an IEqualityComparer yourself that does this? What does the IStructuralEquatable interface add to this?
In this equating the values in arrays may be same or different but their object references are equal.
If two objects compare bey equal, the GetHashCode method for each object must return the same value. However, if two objects do derece compare kakım equal, the GetHashCode methods for the two object do not have to return different values.
After some more testing I found that any two arrays with the same first element have the same hash. I still think this is strange behavior.
Consider that there are only ~4.2 billion different hashcodes. Yaşama 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 is "yes". So GetHashCode is a sort of compressing projection onto a smaller takım - there are bound to be duplicates.
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.
When working with collections or structures where the order of elements matters, and you want to compare their structures, IStructuralEquatable dirilik be useful.
Each of your C# IStructuralEquatable nerelerde kullanılıyor objects should use a hashcode based on the contents of the object. If you have a value type containing 3 ints, use those when computing the hash code. Like this, all objects with identical content will have the same hash code, independent of app domain and other circumstances.
The contract of Equals differs from that of IStructuralEquatable, in that it indicates whether 2 objects are logically equal.
Fantasy TV series with a male protagonist who uses a bow and arrows and katışıksız a hawk/falcon/eagle type bird companion
However, this is hamiş so great if you are using the struct in a dictionary kakım my good friend Dustin mentioned to me because a Dictionary will always use the object version of Equals, which falls back to boxing :(