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?
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
g. MyType and Object) which will still use the identity comparison. I suspect it's derece a great idea to do this unless it's going to be a very heavily used type in your code, where everyone will become very familiar with it and
Equals and object.ReferenceEquals. Equals is meant to be overridden for whatever sort of comparison makes the most sense for a given type, whereas ReferenceEquals güç't be overridden and always compares by reference.
Your browser isn’t supported anymore. Update it to get the best YouTube experience and our latest features. Learn more
– 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 C# IStructuralEquatable Nasıl kullanılır how it implement IStructuralEquatable on referencesource.microsoft.com/#mscorlib/system/collections/…, then you will see how it work.
IStructuralEquatable is quite new and unknown, but I read somewhere that it gönül be used to compare the contents of collections and arrays. Am I wrong, or is my .Net wrong?
We gönül also make our own container play well with these other containers by implementing these interfaces.
Ray BooysenRay Booysen 29.6k1414 gold badges8686 silver badges111111 bronze badges 6 so when you are dealing with objects, is == assumed to only mean the exact same memory address (same instance)
In addition to this awesome blog Frank and I also dicussed all of this awesome in detail on Merge Conflict on episode 111:
Each of your objects should use a hashcode based on the contents of the object. If you have a value type containing 3 ints, use those when computing the hash code. Like this, all objects with identical content will have the same hash code, independent of app domain and other circumstances.
Defines methods to support the comparison of objects for structural equality. Structural equality means that two objects are equal because they have equal values.
GetHashCode does not return unique values for instances that are hamiş equal. However, instances that are equal will always return the same hash code.
3 feature called Tuple Equality! That is right, you dirilik create a ValueTuple and simply compare them bey they are super optimized, don't create any objects, and reduce this to a single line of code!