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?
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This is really amazing code and works great for .Kupkuru Standard libraries. If you are in a .Kupkuru Core 2.1 application there is an even cooler way of doing this:
Does anyone know what happens if you do derece implement iequtalable when using generic collections? 2
I'm amazed that the most important reason is hamiş mentioned here. IEquatable was introduced mainly for structs for two reasons:
Structural equality means that two objects are equal because they have equal values. It differs from reference equality, which indicates that two object references are equal because they reference the same physical object. The IStructuralEquatable interface enables you to implement customized comparisons to check for the structural equality of collection objects.
The IEquatable implementation will require one less cast for these classes and birli a result will be slightly faster than the standard object.Equals method that would be used otherwise. Kakım an example see the different implementation of the two methods:
In my implementation I delegated the task of calculating hash codes to the internal array. While testing it, to my great surprise, I found that my two different arrays had the same structural hash code
The reason why you need the IStructuralEquatable is for defining a new way of comparision that would be right for all the objects .
In Xamarin.Essentials we use the C# struct all over the place to encapsulate "small groups of related variables" for our event handlers. They are groups of data that don't need to be created by the developers consuming the data and are only really used for reading the veri.
Each of your 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.
IStructuralEquatable is used with arrays to determine whether the arrays are structurally equal. The StructuralEqualityComparer.Equals method is used for this purpose.
You observations does not conflict with the documentation and there is no bug in the implementation.
Bunun tarafı nöbet, IStructuralComparable arayüzü, C# IStructuralEquatable Kullanımı izlenceınızı elan modüler hale getirir ve kod yineını azaltır. Farklı veri kuruluşları arasında konstrüktif alınlaştırma emeklemlerini nazar boncuğu bir yerde yönetebilir ve kodunuzun hizmetını kolaylaştırabilirsiniz.