C# IStructuralEquatable Temel Özellikleri - Genel Bakış

C# IStructuralEquatable Temel Özellikleri - Genel Bakış

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.

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.

It differs from reference equality, which indicates that two object references are equal because they reference the same physical object.

IStructuralEquatable is an interface in C# that defines methods for determining whether two objects are structurally equal. It's often used in scenarios where you want to compare the structure of objects, typically within collections, and not just compare references or individual values.

In this equating the values in arrays may be same or different but their object references are equal.

I never put much thought into using a struct over a class or even additional optimizations because to me the struct was optimized already. When I was working on fixing a bug in our DeviceDisplay to not trigger new events unless a value changed a whole new world opened up to me.

IStructuralEquatable is quite new and unknown, but I read somewhere that it can be used to compare the contents of collections and arrays. Am I wrong, or is my .Net wrong?

Defines a generalized method that a value type or class implements to create a type-specific method for determining equality of instances.

The reason why you need the IStructuralEquatable is for defining a new way of comparision that would be right for all the objects .

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 başmaklık 8 upvotes, it is wrong. After a lot of 'reflector'ing, C# IStructuralEquatable Temel Özellikleri here is my take on things.

Amma velakin bu özümlemeız class denli kompleks ustalıklemler ciğerin tasarlanmış bir yapı gerektirmiyorsa ve tutulacak verileri enkapsüle buyurmak yetiyorsa ahacık bu ezgi durumlarda struct yapkaloriı yeğleme edebiliriz.

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 hamiş even compile. So this is a very weak excuse for having a non-generic interface that works with objects.

Specifically, I do hamiş know the exact type of the object. The only assumption I make is that it inherit from IStructuralEquatable.