> I think this issue is related to using > defrecord > or > defrecord & defprotocol > or > defrecord, defprotocol, & extend-protocol > > I've never bothered to look into the simplest case at which it fails. I have > a namespace that has my defrecord, and another namespace that defines the > protocol and uses extend-protocol to add behavior for my record type. If I > recompile the namespace with the protocol everything is fine, if I recompile > the namespace with the defrecord the protocol stops finding the > implementation for the protocol. The solution is "rm -rf classes" > > As a work around I rm & restart my app if I ever change my record - which is > very rarely.
A better solution is not to compile defrecords during development. If this is the default behavior of some tools, it is anti-incremental-dev and wrong IMO. Stu Stuart Halloway Clojure/core http://clojure.com -- 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
