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.

= to provide value equality checks (vs the default reference equality check). The MSDN documentation suggests you only do it for immutable types. There are also issues involving interfaces and operator overloading.

g. MyType and Object) which will still use the identity comparison. I suspect it's not a great idea to do this unless it's going to be a very heavily used type in your code, where everyone will become very familiar with it and

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.

Although I think the gains from not boxing will be less than the cost for having CanEqual. In that case you should seal your types and you no longer need CanEqual. Sealing also özgü some performance benefits.

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

Is Légal’s reported “psychological trick” considered fair play or unacceptable conduct under FIDE rules?

Defines a generalized method that a value type or class implements to create a type-specific method for determining equality of instances.

Reading through the excellent blog post by Sergey on struct equality performance he mentions that the default implementations are pretty slow and using boxing for each member. Additionally, he mentions that a memory comparison may hamiş give you the correct results in this super simple example:

Bu örnekte, articles1 ve articles2 dizileri aynı makale esaslıklarına aynı sırada ehil olduğundan, CompareTo metodu 0 döndürerek bu dizilerin konstrüktif olarak hemayar olduğunu belirtir.

Fakat, fruits1 ve fruits3 dizileri aynı elemanlara farklı sıralarda ehil olduğundan, CompareTo metodu farklı bir kıymetiharbiye döndürür ve bu dizilerin strüktürel olarak denktaş olmadığını belirtir.

The contract of Equals differs from that of IStructuralEquatable, in that it indicates whether 2 objects are logically equal.

Here the comparison is different for value C# IStructuralEquatable Temel Özellikleri type arrays and custom arrays. In .Safi 4.0 int, string will internally implement IEquatable for custom types we have to externally implement the IEquatable.

Specifically, I do hamiş know the exact type of the object. The only assumption I make is that it inherit from IStructuralEquatable.