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 birli using the value type bey a key in a dictionary) it hayat 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.
Equals and object.ReferenceEquals. Equals is meant to be overridden for whatever sort of comparison makes the most sense for a given type, whereas ReferenceEquals sevimli't be overridden and always compares by reference.
Bildiğiniz kabil new işletmenü classlarda kullanıldığı gün müteallik classtan bir nesne istem edilmekte ve üretilen nesne belleğin Heap kısmında saklama edilmektedir.
The following example defines a NanComparer class that implements the IStructuralEquatable interface. 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.
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.
Defines a generalized method that a value type or class implements to create a type-specific method for determining equality of instances.
Ayrıksı bir ifadeyle, kendi konstrüktif müsavat tanımınızı oluşturabilir ve bu tanımın arabirimi akseptans IStructuralEquatable fail bir koleksiyon türüyle kullanılacağını belirtebilirsiniz. Arabirimin iki üyesi vardır: Equals, tamlanan IEqualityComparer bir uygulamayı kullanarak eşitliği test paha ve GetHashCodeeşit olan nesneler dâhilin aynı karma kodları döndürür.
I had the same question. When I ran LBushkin's example I was surprised to see that I got a different answer! Even though that answer has 8 upvotes, it is wrong. After a C# IStructuralEquatable Kullanımı lot of 'reflector'ing, here is my take on things.
This member is an explicit interface member implementation. It dirilik be used only when the Array instance is cast to an IStructuralEquatable interface.
IStructuralEquatable is used with arrays to determine whether the arrays are structurally equal. The StructuralEqualityComparer.Equals method is used for this purpose.
Are the bonuses for infernal war machine weapon stations static, or are they affected by their user?
The Equals method supports custom structural comparison of array and tuple objects. This method in turn calls the comparer object's IEqualityComparer.Equals method to compare individual array elements or tuple components, starting with the first element or component.