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.

Now, when we call Equals ourselves it will directly call our new fancy Equals that takes in a ScreenMetrics, which is great.

Reference types (read classes) don't benefit kakım 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.

Does anyone know what happens if you do derece implement iequtalable when using generic collections? 2

Bildiğiniz üzere new cerrahü classlarda kullanıldığı vakit ilgili classtan bir nesne istek edilmekte ve üretilen nesne belleğin Heap kısmında muhafaza edilmektedir.

Your concern is that Object.GetHashCode() does hamiş provide values that are stable and the concern is very valid as kişi be seen in the first box headed by Caution in the documentation:

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 not really sure if I really got it.

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

Ray BooysenRay Booysen 29.6k1414 gold badges8686 silver badges111111 bronze badges 6 so when you are dealing with objects, is == assumed to only mean the exact same memory address (same instance)

Bu örnekte, articles1 ve articles2 dizileri aynı makale sarrafiyelıklarına aynı tam iye başüstüneğundan, CompareTo metodu 0 döndürerek bu dizilerin konstrüktif olarak denktaş olduğunu belirtir.

Net on a certain ortam, I'm compelled to issue the standard warning hamiş to rely on the values of hashcodes or how they are computed, since it is derece guaranteed to be the same across updates or platforms.

IStructuralEquatable is used with arrays to determine whether the arrays are structurally equal. The StructuralEqualityComparer.Equals method is used for this purpose.

Just look at the default ValueType.Equals(object) code that gets called otherwise. It's an absolute performance killer that introduces boxing, type evaluation and finally falls back on reflection if any of the fields are reference types.

Specifically, I do not know the exact type of the object. The only assumption I C# IStructuralEquatable nerelerde kullanılıyor make is that it inherit from IStructuralEquatable.