On Sat, Jun 9, 2012 at 9:04 PM, Orion Hickman <irespondpromptlywhencontac...@gmail.com> wrote: > This one threw me, hard. I do all my development with a long running > process (as, I'm sure, most people do). Is there some way we can tweak > the implementation to avoid this problem?
Unfortunately defonce semantics on defmulti is intentional. Usually what I do as a workaround is clear the defmulti right before defining it: (def mymulti nil) (defmulti mymulti type) Ugly but preferable to the alternative. I believe the motivation behind the current behaviour is to preserve the method table upon reload; the unchanging dispatch function may just be collateral damage. I haven't looked at the implementation of defmulti, but it may be possible to have reloads change the dispatch function without clearing the method table. -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 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
