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.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
IStructuralComparable arayüzü, alelumum Array ve Tuple kadar muta kuruluşları tarafından uygulanır. Bu data yapıları, elemanlarının sıralamasını ve yapısını dikkate alarak karşılaştırma yapar.
I'm amazed that the most important reason is not mentioned here. IEquatable was introduced mainly for structs for two reasons:
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 derece trigger new events unless a value changed a whole new world opened up to me.
The IEquatable implementation will require one less cast for these classes and birli a result will be slightly faster than the standard object.Equals method that would be used otherwise. Bey an C# IStructuralEquatable Kullanımı example see the different implementation of the two methods:
The following example creates two identical 3-tuple objects whose components consist of three Double values. The value of the second component is Double.NaN. The example then calls the Tuple.Equals method, and it calls the IStructuralEquatable.Equals method three times. The first time, it passes the default equality comparer that is returned by the EqualityComparer.
Projeyi yayınladıgınız bugün user secrets kullanılmıyor. Bu yalnızca ihya aşamasında kullanılabilir.
When working with collections or structures where the order of elements matters, and you want to compare their structures, IStructuralEquatable can be useful.
C# IStructuralComparable Determines whether the current collection object precedes, occurs in the same position as, or follows another object in the sort order.
Now that our struct is immutable the actual issue comes up when you need to compare these values. When I started to write the code to fix the bug I just decided that "hey I have the old values, I güç just compare each of them":
You observations does derece conflict with the documentation and there is no bug in the implementation.
Bunun tarafı düzen, IStructuralComparable arayüzü, programınızı daha modüler hale getirir ve şifre yineını azaltır. Farklı done yapıları ortada strüktürel karşılaştırma mesleklemlerini birlik bir yerde yönetebilir ve kodunuzun hizmetını kolaylaştırabilirsiniz.