Yes, please vote for that issue. I find myself frequently having to work around this limitation of records in Clojure; I mostly avoid using records directly as a consequence of this performance issue.
As a side note, one quick-and-dirty way to get identity semantics for your data is to wrap each piece of data in your application in a delay or atom. The wrapper will give all your data a unique identity-based hash value and equality semantics. On Thu, Jun 11, 2015 at 12:29 PM, Andy Fingerhut <andy.finger...@gmail.com> wrote: > If the reason that defrecord hashing is slow in your application is > because _hasheq_ recalculates the hash values from scratch each time, > without _caching the value_, consider voting for this ticket so that is > improved in the future: http://dev.clojure.org/jira/browse/CLJ-1224 > > -- 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.
