Thanks Steven, Andy. I feel much better knowing now *why *deftype and defrecord have different performance. I felt that I should prefer defrecord because it's the default, and just in case I needed its extra features. Now I can feel good about using deftype as long as I'm clear about what the tradeoffs are. In fact, in the applications I'm planning now, I can't imagine that I'll need value-based hashing for these objects. On the other hand, it might be useful to have the ability to use other defrecord features such as map->record, but now I can make an intelligent choice about it.
-- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
