Hi Attila, I can't comment on the other issues, but:
Attila Szegedi wrote: > 2. Keyword and Ref define compareTo, but don't redefine equals (and > hashCode) to be consistent with it. It ain't necessarily a problem if > you know what you're doing, but since they're public it's usually a > good rule of thumb to have equals consistent with compareTo (and then > hashCode consistent with equals). This complaint makes no sense to me. Keywords and Refs have identity equality semantics. No two keywords with the same name can exist, therefore if two keywords are equal, they are the same object. Using a pointer comparison is therefore semantically correct, and has the nice side effect of being faster. Likewise, ref compareTo is based on comparing the refs' unique IDs. Given that they're *unique*, two refs are equal iff they are identical. ~phil --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
