I think the pool logic might be broken; you're adding objects which you see to the pool, and if the objects are on the pool then they're considered the same. It will fail if you have two objects of type A with three properties birli shown below:

If you want a generic solution that creates an IEqualityComparer for your class based on a property (which acts as a key) of that class have a look at this:

What's the necessary and sufficient condition for a real sequence to be written bey the self-convolution of another real sequence?

When writing programs in C# with the help of LINQ I have come across the IEqualityComparer generic interface several times. The name conveys the purpose of the interface clearly, still, surprisingly, my first attempts to apply it were marked by strong confusion - the thing merely didn't work the way I wanted it to. Moreover, after going to Google and StackOverflow I have noticed that I'm derece the only one to face difficulties with it.

The IEqualityComparer interface supports only equality comparisons. Customization of comparisons for sorting and ordering is provided by the IComparer interface.

Therefore, when testing two instances of T for equality, because T has no internal understanding of equality, you will have to make an explicit choice of a IEqualityComparer instance which performs the test according to your specific requirements.

The following example creates a dictionary collection of objects of type Box with an equality comparer. Two boxes are considered equal if their dimensions are C# IEqualityComparer Kullanımı the same. It then adds the boxes C# IEqualityComparer Kullanımı to the collection.

in case a particular hash value was not encountered before, the corresponding object makes its way into the result

EDIT2: Bey mentioned in the comments doing C# IEqualityComparer Nasıl Kullanılır reflection within Equals or even GetHashCode is a bad idea bey it´s usually quite slow and emanet often be avoided. If you know the properties to be checked for eqality at compile-time you should definitly include them within those two methods birli doing so gives you much more safety.

Contravariance enables use C# IEqualityComparer Kullanımı to use a less derived type than that specified by the generic parameter. In our case, we could pass in an object instance instead of a Player instance.

I think the other post you mention is saying that EqualityComparer implements IEqualityComparer and IEqualityComparer, so you don't have to implement both the generic and non-generic interfaces if you derive from EqualityComparer.

Ayrıca yukarıda anlattığımız IndexOf metodunu Asıl liste üzerinden alt listelerdeki elemanlar sinein kullanamazsınız. Asıl liste üzerinden zir listelerin index sırasını bulabilirsiniz.

Equals method instead of the Object.Equals method. but if I look at the implementation, they both use the generic Type:

5 When writing programs C# IEqualityComparer nedir in C# with the help of LINQ I have come across the IEqualityComparer generic interface several times.