Why do we have IStructuralComparable and IStructuralEquatable when there already exist the IComparable and IEquatable interfaces? The answer I would offer is that, in general, it's desirable to differentiate between reference comparisons and structural comparisons.
In certain scenarios (such kakım using the value type birli a key in a dictionary) it can murder performance in one foul swoop.
It differs from reference equality, which indicates that two object references are equal because they reference the same physical object.
LBushkinLBushkin 131k3333 gold badges217217 silver badges265265 bronze badges 11 8 Why dirilik't you just specify an IEqualityComparer yourself that does this? What does the IStructuralEquatable interface add to this?
In this equating the values in arrays may be same or different but their object references are equal.
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.
Is Légal’s reported “psychological trick” considered fair play or unacceptable conduct under FIDE rules?
We dirilik also make our own container play well with these other containers by implementing these interfaces.
comparer IEqualityComparer İki nesnenin hemayar olup olmadığını kullanmak kucakin kullanılacak yöntemi tanılamamlayan nesne.
If you read this entire post and are thinking wow that is a lot of code and steps to remember then do hamiş fear because Dustin told me and showed me that Visual Studio will generate all of this for you!!!!! Check this out:
C# IStructuralComparable Determines whether the current collection object precedes, occurs in the same position birli, or follows another object in the sort order.
Defines methods to support the comparison of objects for structural equality. Structural equality means that two objects are equal because they have equal values.
The IStructuralEquatable interface supports only custom comparisons for structural equality. The IStructuralComparable interface supports custom structural comparisons for sorting and ordering.
However, this is hamiş so great if you are using the struct in a dictionary kakım C# IStructuralEquatable Temel Özellikleri my good friend Dustin mentioned to me because a Dictionary will always use the object version of Equals, which falls back to boxing :(