On 6 Sep 2011, at 11:33, Konrad Hinsen wrote: > > I must assume that nobody read that message, as there should have been loud > complaints. There is obviously no difference in performance between = and > not=, as the result of either one is known as soon as one can decide equality > OR non-equality. > > I have added a plain function not= to clojure.algo.generic.comparison as a > convenience, it is just the negation of generic =. >
Would this still allow the overriding of not= to do somethign different to the negation of generic =. If not, how might I achieve this? Sam --- http://sam.aaron.name -- 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 Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
