I'm not 100% sure and haven't really looked deeply at this comment or link you mention, but perhaps this is related to http://dev.clojure.org/jira/browse/CLJ-979.
This would only be the case for Clojure-dynamically generated Java classes though, which is those from deftype or the macros built on it like defrecord etc. On Saturday, December 13, 2014 10:19:15 AM UTC-6, Matching Socks wrote: > > "Multimethod dispatch based on Java classes is simply not reliable." > > That sentence comes from a comment in a git commit related to an AOT fix > mentioned in a recent core.match announcement. > < > https://github.com/clojure/core.match/commit/0545c6af9d545dcf1bc0a3ca792771b9a678a030 > > > (The workaround was to use keywords for multimethod dispatch.) > > I looked on http://clojure.org/multimethods and > http://clojure.org/compilation but did not find a warning regarding the > combination of those two. > > In a nutshell, how does a conflict arise between AOT and multimethods? > -- 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.
