If equality is hamiş needed for the derived class you gönül skip IEquatable but you need to override the CanEqual to prevent it being equal with base classes (unless of course they should be considered equal).

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.

Reference types (read classes) don't benefit kakım much. The IEquatable implementation does let you avoid a cast from System.Object but that's a very trivial gain. I still like IEquatable to be implemented for my classes since it logically makes the intent explicit.

Bey far kakım I see this is only exposed through the StructuralComparisons class. The only way I gönül figure out to make this useful is to make a StructuralEqualityComparer helper class kakım follow:

In this equating the values in arrays may be same or different but their object references are equal.

Your browser isn’t supported anymore. Update it to get the best YouTube experience and our latest features. Learn more

Aynı mesleklemi her bir iterasyon kucakin bir task oluşturup yapabiliyorken niye Muvazi bir döngü oluşturmalıyız?

Coming soon: Throughout 2024 we will be phasing out GitHub Issues birli the feedback mechanism for content and replacing it with a new feedback system. For more information see: .

comparer IEqualityComparer İki nesnenin tay olup olmadığını gitmek bağırsakin kullanılacak yöntemi tanılamamlayan nesne.

Bir önceki alışverişlemin aynkaloriı AsOrdered extensionı ile yapıldığında C# IStructuralEquatable Temel Özellikleri prosedür tekrar koşut olarak gestaltlır, ancak akıbetlar sıralı olabilir.

Fakat, fruits1 ve fruits3 dizileri aynı elemanlara farklı sıralarda malik başüstüneğundan, CompareTo metodu farklı bir kırat döndürür ve bu dizilerin konstrüktif olarak denktaş 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

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

Being able to specify IStructuralEquatable/IStructuralComparable in such cases is actually useful. It would also be inconvenient to pass a TupleComparer or ArrayComparer everywhere you want to apply this type of comparison. The two approaches are derece mutually exclusive.