comparer IEqualityComparer An object that determines whether the current instance and other are equal.
Now, when we call Equals ourselves it will directly call our new fancy Equals that takes in a ScreenMetrics, which is great.
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.
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. Bey the output from the example shows, the first three method calls return true, whereas the fourth call returns false.
I'm amazed that the most important reason is hamiş mentioned here. IEquatable was introduced mainly for structs for two reasons:
comparer IEqualityComparer An object that determines whether the current instance and other are equal.
1 My understanding is that it's used for collection like types, and encapsulates the structural part of the comparison, but leaved the comparison of the elements to a comparer passed in by the user. But I'm derece really sure if I really got it.
In my implementation I delegated the C# IStructuralEquatable nerelerde kullanılıyor 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
comparer IEqualityComparer İki nesnenin eşit olup olmadığını kıymetlendirmek karınin kullanılacak yöntemi teşhismlayan nesne.
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 veri that don't need to be created by the developers consuming the veri and are only really used for reading the data.
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.
Specifically, I do derece know the exact type of the object. The only assumption I make is that it inherit from IStructuralEquatable.