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.
Bu sayede, muta örgülarının kucakindeki verilerin sıralanması yahut mukabillaştırılması işçiliklemleri özelleştirilebilir ve kontrol edilebilir hale gelir.
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
Daniel A.A. PelsmaekerDaniel A.A. Pelsmaeker 49.2k2121 gold badges112112 silver badges160160 bronze badges 5 In addition to answers which point to duplicate hashcodes kakım is documented behavior, some reasoning and reflection would also lead you to the same conclusion.
Let us not forget about additional operators and not just relying on Equals. We hayat implement the == and != operators easily:
– Royi Namir Commented Mar 3, 2012 at 18:04 @RoyiNamir user844541's answer is correct, but maybe it is still hard for you to understand without a concrete example, if you are familiar with IEqualityComparer and how it is used by Linq's Distinct(), then after check the source code to see how it implement IStructuralEquatable on referencesource.microsoft.com/#mscorlib/system/collections/…, then you will see how it work.
The IStructuralEquatable interface enables you to implement customized comparisons to check for the structural equality of collection objects. This is also made clear by the fact that this interface resides in the System.Collections namespace.
I've noticed these two interfaces, and several associated classes, have been added in .NET 4. They seem a bit superfluous to me; I've read several blogs about them, but I still hayat't figure out what sorun they solve that was tricky before .Kupkuru 4.
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)
In addition to this awesome blog Frank and C# IStructuralEquatable Temel Özellikleri I also dicussed all of this awesome in detail on Merge Conflict on episode 111:
C# IStructuralEquatable Defines methods to support the comparison of objects for structural equality.
That is, you kişi create your own definition of structural equality and specify that this definition be used with a collection type that accepts the IStructuralEquatable interface. The interface özgü two members: Equals, which tests for equality by using a specified IEqualityComparer implementation, and GetHashCode, which returns identical hash codes for objects that are equal.
Here the comparison is different for value type arrays and custom arrays. In .Kemiksiz 4.0 int, string will internally implement IEquatable for custom types we have to externally implement the IEquatable.
3 feature called Tuple Equality! That is right, you kişi create a ValueTuple and simply compare them kakım they are super optimized, don't create any objects, and reduce this to a single line of code!