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.
This is really amazing code and works great for .NET Standard libraries. If you are in a .Safi Core 2.1 application there is an even cooler way of doing this:
IStructuralComparable arayüzü, genellikle Array ve Tuple üzere veri bünyeları tarafından uygulanır. Bu bilgi konstrüksiyonları, elemanlarının sıralamasını ve yapkaloriı dikkate alarak önlaştırma yapar.
In this equating the values in arrays may be same or different but their object references are equal.
If two objects compare bey equal, the GetHashCode method for each object must return the same value. However, if two objects do derece compare bey equal, the GetHashCode methods for the two object do not have to return different values.
The IEquatable implementation will require one less cast for these classes and bey a result will be slightly faster than the standard object.Equals method that would be used otherwise. As an example see the different implementation of the two methods:
Yani anlayacağınız “int” kabilinden, “bool” gibi porte tipli bir değişebilir tekvin etmek istiyorsanız struct yapısını yeğleme edebilirsiniz.
(doesn't violate documentation), but it is clearly not bey good kakım it would be if 0 were replaced with i. Also there's no reason to loop if the code were just going to use a single value from the array.
In all my years of development and blogging I never thought I would be writing about how amazing a C# struct is, how awesome IEquatable is, and how C# 7 features make implementing all of it mind blowing.
Fakat, fruits1 ve fruits3 dizileri aynı elemanlara C# IStructuralEquatable Nasıl kullanılır farklı sıralarda malik evetğundan, CompareTo metodu farklı bir valör döndürür ve bu dizilerin yapısal 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.