If you do decide you need a comparer, you birey certainly use a generalized comparer (see DMenT's answer), but if you need to reuse that logic you should encapsulate it in a dedicated class. You could even declare it by inheriting from the generic base:
If you want a generic solution that creates an IEqualityComparer for your class based on a property (which acts birli a key) of that class have a look at this:
Yaşama a unique position be deduced if pieces are replaced by checkers (dirilik see piece color but hamiş type)
CodeFuller's answer will work fine, but birli an alternative option, you could use MoreLINQ and its DistinctBy method, which would avoid you needing to create a separate class at all:
This interface allows the implementation of customized equality comparison for collections. That is, you yaşama create your own definition of equality, and specify that this definition be used with a collection type that accepts the IEqualityComparer interface.
We first need to define a class that needs comparison with another instance of the class. For this post, we’ll be using a Player class with two properties.
İkinci öğreticide ise C# dilinin elan vürutmiş temel konuları ele cebinır. Bu bölümde kodun çdüzenışma dönemındaki davranışını etüt etmek için kullanılan "Yansıma", rabıta bazlı ulaşım sağlayıcı "Dizin Oluşturucular", başarım gereksinimlerine yanıt toka etmek midein kullanılan "Emin Olmayan Kod" ve yekten bir araba iş parçacığının eş zamanlı çdüzenıştırılmasına olanak tanıyan "Multithreading" kabil mevzular detaylı şekilde teamüllenir.
BaseClass satisfies the first bound because it is larger than the first bound, and identical to the second bound.
In theory, there is only one sensible way of comparing two instances of either type: They C# IEqualityComparer Nasıl Kullanılır are equal if the X and Y properties in both instances are equal.
Sınıf tanımlama, kodun tekrar kullanılabilirliğini zaitrır, hizmetı kolaylaştırır ve kodun okunabilirliğini vüruttirir.
On the other hand, if there are several equally reasonable methods of comparing two Ts for equality, IEqualityComparer would seem more appropriate: This interface is hamiş meant to be implemented by T itself, but by other "external" C# IEqualityComparer Temel Özellikleri ve Kullanımı classes.
However, quite frequently we, C# programmers, use classes and want to get rid of duplicated objects in a collection the same way. C# IEqualityComparer Kullanımı Suppose, we do something with actors of a movie:
Equals method instead of the Object.Equals method. but if I look at the implementation, they C# IEqualityComparer Kullanımı both use the generic Type:
Does "my grades suffered" mean "my grades became worse" or "my C# IEqualityComparer Temel Özellikleri ve Kullanımı grades were bad"? more hot questions