You get a nice simple bool Equals(T other) function and there's no messing around with casting or creating a separate class.
If you want a generic solution that creates an IEqualityComparer for your class based on a property (which acts kakım a key) of that class have a look at this:
Temel komut satırı icraatından kompleks işlemlevselliklere mevla pusatlara denli her şeyi C# ile tasarlayabilirsin.
next, when we iterate over the query object it gets hash code for each item in the source collection and compares it with the hashes of preceding objects
I particularly feel that the GetHashCode() could do with some improvement, because it doesn't give unique values for objects with different reference objects nested further.
This is because LINQ methods accept IEnumerable as a parameter. Consequently, they have no concept of the implementation of the original list.
It is essentially the same for this purpose with one subtle difference. In your first example you override Equals using C# IEqualityComparer Nasıl Kullanılır a parameter of type Object and then have to cast it to Customer, however, in your second example you are able to have the parameter of type Customer which means there is no need to cast.
There are multiple ways to tackle this and tell LINQ how the objects should be compared C# IEqualityComparer nedir to each other. I will cover the use of IEqualityComparer. The interface contains two methods:
In theory, there is only one sensible way of comparing two instances of either type: C# IEqualityComparer nedir They are equal if the X and Y properties in both instances are equal.
Eric's answer explains the root cause of the whole C# IEqualityComparer Nasıl Kullanılır issue (in terms of covariance and contravariance).
When we make the inference from the comparer we say "IEqualityComparer is contravariant in T, C# IEqualityComparer nedir so we emanet accept BaseClass or any smaller type
The Equals(T, T) method is reflexive, symmetric, and transitive. That is, it returns true if used to compare an object with itself; true for two objects x and y if it is true for y and x; and true for two objects x and z if it is true for x and y and also true for y and z.
Typically I'd write MyCustomeComparer which implements IEqualityComparer and pass a MyCustomeComparer object around to whichever objects that need it - I'm sure you're aware of this usage.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.