Related - does using a purer approach hurt debugging and error comprehension on the host - JVM / JavaScript?
On Thu, Sep 5, 2013 at 1:28 PM, David Nolen <dnolen.li...@gmail.com> wrote: > On Thu, Sep 5, 2013 at 1:23 PM, Timothy Baldridge <tbaldri...@gmail.com>wrote: > >> I used to think the same, until I wrote the current incarnation of the go >> macro in core.async. A few months back I ripped out all global vars (and >> bindings). The go "compiler" is now functionally pure, except for a single >> atom on the edge that counts locals. More and more I'm convinced that >> dynamic vars, while pragmatic, are used way more often than they should be. >> > > How easy it to add a new bit of dynamic context using your state monad > without modifying the original code. Does everyone upstream need to be > lifted? > > David > > -- -- 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.
