2 Dakika Kural için C# IStructuralEquatable Nasıl kullanılır

2 Dakika Kural için C# IStructuralEquatable Nasıl kullanılır

Blog Article

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?

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.

This is really amazing code and works great for .NET Standard libraries. If you are in a .Kemiksiz Core 2.1 application there is an even cooler way of doing this:

IStructuralEquatable is an interface in C# that defines methods for determining whether two objects are structurally equal. It's often used in scenarios where you want to compare the structure of objects, typically within collections, and hamiş just compare references or individual values.

It is used by the third example kakım an argument to the Equals(Object, IEqualityComparer) method of the IStructuralEquatable interface that tuples implement. It compares two Double or two Single values by using the equality operator. It passes values of any other type to the default equality comparer.

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.

IStructuralEquatable is quite new and unknown, but I read somewhere that it gönül be used to compare the contents of collections and arrays. Am I wrong, or is my .Net wrong?

This is very disappointing behaviour from Microsoft; I'm now wondering if I should review the list of cases I've filed and see if other ones I've submitted have been removed...

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 all my years of development and blogging I never thought I would be writing about how amazing a C# struct is, how awesome IEquatable is, and how C# 7 features make implementing all of it mind blowing.

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

The example on MSDN gives part of the answer here; it seems to be useful for heterogeneous equality, rather than homogeneous equality - i.e. for testing whether two objects (/values) of potentially different types

The IStructuralEquatable interface supports only custom comparisons for structural equality. The IStructuralComparable interface supports custom structural comparisons for sorting and ordering.

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