2 Dakika Kural için C# IStructuralEquatable Nasıl kullanılır

2 Dakika Kural için C# IStructuralEquatable Nasıl kullanılır

Blog Article

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.

= to provide value equality checks (vs the default reference equality check). The MSDN documentation suggests you only do it for immutable types. There are also issues involving interfaces and operator overloading.

Reference types (read classes) don't benefit birli 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.

Daniel A.A. PelsmaekerDaniel A.A. Pelsmaeker 49.2k2121 gold badges112112 silver badges160160 bronze badges 5 In addition to answers which point to duplicate hashcodes kakım is documented behavior, some reasoning and reflection would also lead you to the same conclusion.

Although I think the gains from hamiş 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 özgü some performance benefits.

comparer IEqualityComparer An object that determines whether the current instance and other are equal.

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 hamiş really sure if I really got it.

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

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

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:

To achieve this, employee objects with matching SSN properties would be treated as logically equal, even if they were derece structurally equal. Share Improve this answer Follow

The contract of Equals differs from that of IStructuralEquatable, in that it indicates whether 2 objects are logically equal.

There is no need for an equality operator that accepts different types. That should derece even compile. So this is a very weak excuse for having a non-generic interface that works with objects.

However, this is derece so great if you are using the struct in a dictionary birli my good friend Dustin mentioned to me because a Dictionary will always use the object version of Equals, which falls back to boxing :(