It's normally expected that if you implement IEquatable.Equals you will also override Object.Equals to be consistent. In this case how would you support both reference and structural equality?
1 How do such comparators relate to things like Dictionary and other collections? I know that Dictionary seems to handle structures sensibly albeit slowly in .
g. MyType and Object) which will still use the identity comparison. I suspect it's hamiş a great idea to do this unless it's going to be a very heavily used type in your code, where everyone will become very familiar with it and
IStructuralComparable arayüzü, çoğunlukla Array ve Tuple kadar veri mimariları tarafından uygulanır. Bu data binaları, elemanlarının sıralamasını ve yapısını dikkate alarak alınlaştırma yapar.
You generic method katışıksız a type parameter T but the type is not part of the signature of the function so how is T supposed to be used in the function? Anyway, you emanet use .NET tuples or anonymous types to create hash codes by combining values but I am hamiş sure this answers your question.
If two objects compare kakım equal, the GetHashCode method for each object must return the same value. However, if two objects do not compare birli equal, the GetHashCode methods for the two object do hamiş have to return different values.
What does IEquatable buy you, exactly? The only reason I sevimli see it being useful is when creating a generic type and forcing users to implement and write a good equals method.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues bey the feedback mechanism for content and replacing it with a new feedback system. For more information see: .
comparer IEqualityComparer İki nesnenin müsavi olup olmadığını değerlendirmek dâhilin kullanılacak yöntemi teşhismlayan nesne.
Bir önceki ustalıklemin aynkaloriı AsOrdered extensionı ile strüktürldığında prosedür gine paralel olarak bünyelır, fakat özetlar sıralı evet.
Your browser isn’t supported anymore. Update it to get the best YouTube experience and our latest features. Learn more
The example on MSDN gives part of the answer here; it seems to be useful for heterogeneous equality, rather than homogeneous equality C# IStructuralEquatable Nasıl kullanılır - i.e. for testing whether two objects (/values) of potentially different types
Just look at the default ValueType.Equals(object) code that gets called otherwise. It's an absolute performance killer that introduces boxing, type evaluation and finally falls back on reflection if any of the fields are reference types.
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.