Thanks for the pointer to tools.namespace<https://github.com/clojure/tools.namespace> — it looks really useful. And if I follow the advice there to "always create new instances of records after a refresh", it will simplify my decision on how to organise namespaces — there's no longer a need to separate protocols and their implementations. Now I only need to think about how to make it easy to create new instances of records after a refresh :-)
On Monday, 15 April 2013 19:45:45 UTC+1, Stuart Sierra wrote: > > "...talk by Stuart Sierra (http://vimeo.com/46163090) in which he >> suggests putting protocols and their implementations in separate >> namespaces, because, during development reloading a protocol breaks >> existing instances" >> > > I don't universally recommend this any more. You still have to be careful > with reloading. The documentation for > tools.namespace<https://github.com/clojure/tools.namespace>describes some the > issues with reloading and protocols, and ways to work > around them. > > -S > > -- -- 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/groups/opt_out.
