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.

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.

. The best example of this is arrays, which with .Safi 4 now implement the IStructuralEquatable interface. This makes it possible to distinguish whether you are comparing two arrays for reference equality, or for "structural equality" - whether they have the same number of items with the same values in each position. Here's an example:

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.

I'm amazed that the most important reason is not mentioned here. IEquatable was introduced mainly for structs for two reasons:

The generic tuple classes (Tuple, Tuple, Tuple, and so on) and the Array class provide explicit implementations of the IStructuralEquatable interface. By casting (in C#) or converting (in Visual Basic) the current instance of an array or tuple to an IStructuralEquatable interface value and providing your IEqualityComparer implementation birli an argument to the Equals method, you kişi define a custom equality comparison for the array or collection.

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.

We hayat also make our own container play well with these other containers by implementing these interfaces.

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:

Amma velakin bu konstrüksiyonız class denli kompleks teamüllemler için tasarlanmış bir yapı gerektirmiyorsa ve tutulacak verileri enkapsüle geçirmek yetiyorsa aha bu şekil durumlarda struct yapısını tercih edebiliriz.

The contract of Equals differs from that of IStructuralEquatable, in that it indicates whether 2 objects are logically equal.

Is there any yasal justification for content on the web without an explicit licence being freeware? more hot questions

Specifically, I do C# IStructuralEquatable nedir derece know the exact type of the object. The only assumption I make is that it inherit from IStructuralEquatable.