En C# IStructuralEquatable Kullanımı Sırları

En C# IStructuralEquatable Kullanımı Sırları

Blog Article

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?

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.

Reference types (read classes) don't benefit birli much. The IEquatable implementation does let you avoid a cast from System.Object but that's a very trivial gain. I still like IEquatable to be implemented for my classes since it logically makes the intent explicit.

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 emanet't be overridden and always compares by reference.

Birli 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.

If two objects compare bey 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 return different values.

So, I am apparently wrong as unequal objects may have equal hash codes. But isn't GetHashCode returning a somewhat randomly distributed grup of values a requirement?

This is very disappointing behaviour from Microsoft; I'm now wondering if I should review the list of cases I've filed and see if other ones I've submitted have been removed...

Projeyi yayınladıgınız saat user secrets kullanılmıyor. Bu sadece geliştirme aşamasında kullanılabilir.

Collaborate with us on GitHub The source for this content emanet be found on GitHub, where you kişi also create and review issues and pull requests. For more information, see our contributor guide.

Your browser isn’t supported anymore. Update it to get the best YouTube experience and our latest features. Learn more

Defines methods to support the comparison of objects for structural equality. Structural equality means that two objects are equal because they have equal values.

You observations does derece conflict with the documentation and there is no bug in the implementation.

However, this is hamiş so great if you are using the struct in a dictionary birli my good friend C# IStructuralEquatable Temel Özellikleri Dustin mentioned to me because a Dictionary will always use the object version of Equals, which falls back to boxing :(