5 Basit Teknikleri için C# IStructuralEquatable nerelerde kullanılıyor
5 Basit Teknikleri için C# IStructuralEquatable nerelerde kullanılıyor
Blog Article
It's normally expected that if you implement IEquatable.Equals you will also override Object.Equals to be consistent. In this case how would you support both reference and structural equality?
In certain scenarios (such kakım using the value type bey a key in a dictionary) it birey murder performance in one foul swoop.
It differs from reference equality, which indicates that two object references are equal because they reference the same physical object.
LBushkinLBushkin 131k3333 gold badges217217 silver badges265265 bronze badges 11 8 Why hayat't you just specify an IEqualityComparer yourself that does this? What does the IStructuralEquatable interface add to this?
Although I think the gains from not 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 saf some performance benefits.
– Royi Namir Commented Mar 3, 2012 at 18:04 @RoyiNamir user844541's answer is correct, but maybe it is still hard for you to understand without a concrete example, if you are familiar with IEqualityComparer and how it is used by Linq's Distinct(), then after check the source code to see how it implement IStructuralEquatable on referencesource.microsoft.com/#mscorlib/system/collections/…, then you will see how it work.
IStructuralEquatable is quite new and C# IStructuralEquatable nedir 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.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues kakım the feedback mechanism for content and replacing it with a new feedback system. For more information see: .
When working with collections or structures where the order of elements matters, and you want to compare their structures, IStructuralEquatable güç be useful.
Amma velakin bu prodüksiyonız class denli kompleks anlayışlemler dâhilin tasarlanmış bir yapı gerektirmiyorsa ve tutulacak verileri enkapsüle etmek yetiyorsa aha bu usul durumlarda struct yapısını yeğleme edebiliriz.
Do derece send hash codes across application domains or processes. In some cases, hash codes may be computed on a per-process or per-application domain basis.
Are the bonuses for infernal war machine weapon stations static, or are they affected by their user?
Being able to specify IStructuralEquatable/IStructuralComparable in such cases is actually useful. It would also be inconvenient to pass a TupleComparer or ArrayComparer everywhere you want to apply this type of comparison. The two approaches are hamiş mutually exclusive.