Kevin Downey <redc...@gmail.com> writes: > if I recall, the current defonce like behavior of multimethods was a > response to the situation where if you have your multimethods split > across multiple files reloading the file with the defmulti in it would > re-def the multimethod with the new dispatch, but it would not have > any of the methods loaded from the other files. > > oscillating between these poles at about 6.31139e7hz seems less than ideal. > > maybe defmethod could try and capture the ns a method is defined in, > and defmulti would try to force a reload? seems overly complicated for > core.
I assume there's already a really good reason re-evaling defmulti doesn't just change the dispatch function without blowing away the method table? Though I can't think of one myself. -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
