Hakkında herşey C# IStructuralEquatable Temel Özellikleri

Hakkında herşey C# IStructuralEquatable Temel Özellikleri

Blog Article

If equality is not needed for the derived class you dirilik skip IEquatable but you need to override the CanEqual to prevent it being equal with base classes (unless of course they should be considered equal).

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.

This is really amazing code and works great for .Safi Standard libraries. If you are in a .Kupkuru Core 2.1 application there is an even cooler way of doing this:

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

I'm amazed that the most important reason is derece mentioned here. IEquatable was introduced mainly for structs for two reasons:

The IStructuralEquatable interface enables you to implement customized comparisons to check for the structural equality of collection objects.

What does IEquatable buy you, exactly? The only reason I yaşama see it being useful is when creating a generic type and forcing users to implement and write a good equals method.

I've noticed these two interfaces, and several associated classes, have been added in .Safi 4. They seem a bit superfluous to me; I've read several blogs about them, but I still yaşama't figure out what sorun they solve that was tricky before .Kupkuru 4.

Projeyi yayınladıgınız vakit user secrets kullanılmıyor. Bu yalnızca geliştirme aşamasında kullanılabilir.

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 saf 8 upvotes, it is wrong. After a lot of 'reflector'ing, here is my take on things.

C# IStructuralComparable Determines whether the current collection object precedes, occurs in the same position kakım, or follows another object in the sort order.

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

Are the bonuses for infernal war machine weapon C# IStructuralEquatable Kullanımı stations static, or are they affected by their user?

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