C# IStructuralEquatable nerelerde kullanılıyor Herkes İçin Eğlenceli Olabilir

C# IStructuralEquatable nerelerde kullanılıyor Herkes İçin Eğlenceli Olabilir

Blog Article

The "No" in part 2 of the answer is actually incorrect. Note: Tried editing the answer, but apparently some think that the highest rated answer being incorrect is not reason enough to approve a correction edit.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Other types which implement structural equality/comparability include tuples and anonymous types - which both clearly benefit from the ability to perform comparison based on their structure and content. A question you didn't ask is:

LBushkinLBushkin 131k3333 gold badges217217 silver badges265265 bronze badges 11 8 Why gönül't you just specify an IEqualityComparer yourself that does this? What does the IStructuralEquatable interface add to this?

Let us not forget about additional operators and not just relying on Equals. We sevimli implement the == and != operators easily:

45IStructuralEquatable seObj = x kakım IStructuralEquatable; 64IStructuralEquatable seObj = obj as IStructuralEquatable;

1 My understanding is that it's used for collection like types, and encapsulates the structural part of the comparison, but leaved the comparison of the elements to a comparer passed in by the user. But I'm hamiş really sure if I really got it.

When an implementer overrides the virtual Equals method in a struct, the purpose is to provide a more efficient means of performing the value equality check and optionally to base the comparison on some subset of the struct's field or properties.

The reason why you need the IStructuralEquatable is for defining a new way of comparision that would be right for all the objects .

In addition to this awesome blog Frank and 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.

Now that our struct is immutable the actual issue comes up when you need to compare these values. When I started to write the code to fix the bug I just decided that "hey I have the old values, I dirilik just compare each of them":

You observations does derece conflict with the documentation and there is no bug in the implementation.

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 C# IStructuralEquatable nedir individual array elements or tuple components, starting with the first element or component.