Why do we have IStructuralComparable and IStructuralEquatable when there already exist the IComparable and IEquatable interfaces? The answer I would offer is that, in general, it's desirable to differentiate between reference comparisons and structural comparisons.
In this case you don't want to change your class implementation so you don't wantoverride the Equals method. this will define a general way to compare objects in your application.
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.
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.
Although I think the gains from derece boxing will be less than the cost for having CanEqual. In that case you should seal your types and you no longer need CanEqual. Sealing also has some performance benefits.
Your concern is that Object.GetHashCode() does not provide values that are stable and the concern is very valid bey hayat be seen in the first box headed by Caution in the documentation:
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 not really sure if I really got it.
Consider that there are only ~4.2 billion different hashcodes. Sevimli you create more than this many different objects of the type on which GetHashCode is called? In this case it is easy to see the answer is "yes". So GetHashCode is a sort of compressing projection onto a smaller kaş - there are bound to be duplicates.
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)
If you read this entire post and are thinking wow that is a lot of code and steps to remember then do hamiş fear because Dustin told me and showed me that Visual Studio will generate all of this for you!!!!! Check this out:
Programlama dillerinde en mühim OOP(Object Oriented Programing) binalarından olan class binasına nazaran daha basit düzeyde fiillemler gerçekleştirmemizi sağlayıcı ve mukannen bir ekipman kısıtlamaları yanında barındıran struct yapısını C# diline özel ele alacağız.
IStructuralEquatable is used with arrays to determine whether the arrays are structurally equal. The C# IStructuralEquatable Nasıl kullanılır StructuralEqualityComparer.Equals method is used for this purpose.
You observations does derece conflict with the documentation and there is no bug in the implementation.
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.