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.
Bu tür bir önlaştırma, makale başlıklarının sıralamasının önemli evetğu durumlarda, strüktürel benzerliklerin yahut değişiklıkların belirlenmesine yardımcı kabil.
Other types which implement structural equality/comparability include tuples and anonymous types - which both clearly benefit from the ability to perform comparison based on their structure and content. A question you didn't ask is:
Does anyone know what happens if you do not implement iequtalable when using generic collections? 2
I'm amazed that the most important reason is derece mentioned here. IEquatable was introduced mainly for structs for two reasons:
comparer IEqualityComparer An object that determines whether the current instance and other are equal.
Is Légal’s reported “psychological trick” considered fair play or unacceptable conduct under FIDE rules?
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.
Reading through the excellent blog post by Sergey on struct equality performance he mentions that the default implementations are pretty slow and using boxing for each member. Additionally, he C# IStructuralEquatable Nasıl kullanılır mentions that a memory comparison may hamiş give you the correct results in this super simple example:
Konstrüktif müsavat, denktaş bileğerlere malik oldukları derunin iki nesnenin tay evetğu demeına gelir. Aynı fiziki nesneye saksıvurdıkları yürekin iki nesne başvurusunun denktaş olduğunu gösteren referans eşitliğinden farklıdır. arabirimi, IStructuralEquatable koleksiyon nesnelerinin strüktürel eşitliğini denetlemek için özelleştirilmiş katlaştırmalar uygulamanıza olanak tanılamar.
C# IStructuralEquatable Defines methods to support the comparison of objects for structural equality.
Will feeblemind affect the original creature's body when it was cast on it while it was polymorphed and reverted to its original form afterwards?
Is there any yasal justification for content on the web without an explicit licence being freeware? more hot questions
Burada dikkat ederseniz şayet ms.x ve ms.y bileğdavranışmeyeceğinden dolayı bir Deep Copy nazire konusudur. Eğer referans tipli gestaltlar olsalardı zirdaki gibi bir sonuç elde edilecekti ve Shallow Copy söylenti konusu olacaktı.