Benim C# IStructuralEquatable Nasıl kullanılır Başlarken Çalışmak

Benim C# IStructuralEquatable Nasıl kullanılır Başlarken Çalışmak

Blog Article

The individual calls to IEqualityComparer.Equals end and the IStructuralEquatable.Equals method returns a value either when a method call returns false or after all array elements or tuple components have been compared.

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.

That is right! When we override Equals we must also override and implement GetHashCode. I am no HashCode expert, but in the same article from Sergey is a snippet of using a ValueTuple to simplify this entire call to 1 line of code just like our fancy ValueTuple Equality above.

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

It is used by the third example kakım an argument to the Equals(Object, IEqualityComparer) method of the IStructuralEquatable interface that tuples implement. It compares two Double or two Single values by using the equality operator. It passes values of any other type to the default equality comparer.

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 bey an argument to the Equals method, you sevimli define a custom equality comparison for the array or collection.

So, I am apparently wrong birli unequal objects may have equal hash codes. But isn't GetHashCode returning a somewhat randomly distributed takım of values a requirement?

In my implementation I delegated the task of calculating hash codes to the internal array. While testing it, to my great surprise, I found that my two different arrays had the same structural hash code

Ray BooysenRay Booysen 29.6k1414 gold badges8686 silver badges111111 bronze badges 6 so when you are dealing with objects, is == assumed to only mean the exact same memory address (same instance)

I had the same question. When I ran LBushkin's example I was surprised to see that I got a different answer! Even though that answer katışıksız 8 upvotes, it is wrong. After a lot of 'reflector'ing, here is my take on things.

GitHub'da bizimle ortaklaşa iş binan Bu dâhilğin kaynağı GitHub'da bulunabilir; burada antrparantez sorunları ve çekme isteklerini oluşturup gözden geçirebilirsiniz. Henüz fazla bili dâhilin katkıda mevcut kılavuzumuzu inceleyin.

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 C# IStructuralEquatable nerelerde kullanılıyor objects (/values) of potentially different types

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

Bu alanda yahut sair bir alanda, benim ve başka yardımcı insanların paylaşımlarına lütfen acizliğiniz ve ezikliğinizle yaklaşmayınız. İzin istemek, benim hükmüm altına girmeniz fehvaına gelmemektedir.