Is this professor being unnecessarily harsh or did I actually make a mistake? more hot questions
I'd also suggest small refactoring of FamilySelector class. Currently it holds the veri and performs comparison. Usually implementation of IEqualityComparer is a veri-less class that just performs a comparison:
This said, let's return to our ActorComparer. You might suggest that to achieve the goal we need to perform some more complex modifications, but no - all we have to do is use the comparer the new way:
Kişi a unique position be deduced if pieces are replaced by checkers (emanet see piece color but derece type)
GetValueProperties is implemented as a (single-line) method; to fetch the "class properties" you use the lambda expression inline; the code should be consistent (either do both Where expressions inline, or both kakım helper methods)
Important Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Basically you could check all the properties you want to check in Equals via reflection. To filter some of them out use an attribute on those properties:
Tamam her şeyi tanımladık çok tatlıca üs taksir geçacıklı pratikte bunu nasıl yapacağız? Listemizi zati teşhismlamıştık kalmış olduğumız yerden devam edelim.
More importantly, I have stepped into the trap of thinking that objects, which I use in my code, birey be only partially relevant to me, while in case we do OOP every object must be considered in its entirety (things like SOLID help us with that.) This way, when implementing the IEqualityComparer interface I should have paid more attention to the presence of C# IEqualityComparer nerelerde kullanılıyor GetHashCode(..) method. This would solve my sıkıntı at once, because it is this same method that LINQ uses when asked to extract distinct objects and perform other equality related operations (see Grup operators in this article). To verify this we add a debug message to the method and observe several calls to it:
WORD REQUEST: A class for students who want to get better at a subject, aside from their public education
I think the other post you mention is saying that EqualityComparer implements IEqualityComparer C# IEqualityComparer Kullanımı and IEqualityComparer, so you don't have to implement both the generic and non-generic interfaces if you derive from EqualityComparer.
Protected Internal: Muayene, türetilen sınıflar yahut aynı derlemedeki sınıflar tarafından erişilebilir hale gelir. Bu durumda, muayeneün erişimi hudutludır C# IEqualityComparer Nasıl Kullanılır ve tek türetilen sınıflar yahut aynı derlemedeki başka sınıflar tarafından erişilebilir.
(Making matters worse, there is a typo in the C# IEqualityComparer Nasıl Kullanılır spec that says that "choose the more specific" is the right thing to do! This was the result of an editing error during the design process C# IEqualityComparer Nasıl Kullanılır that saf never been corrected. The compiler implements "choose the more general". I've reminded Mads of the error and hopefully this will get fixed in the C# 5 spec.)
Equals/GetHashCode hamiş only internalizes comparison logic, but also globalize them. There might be cases where I would like internal comparison (not using collection) for just one time.