On Wednesday, July 23, 2014 at 2:06 AM, Tom Locke wrote: > @Kyle - it's not a deep problem with Clojure extensibility but just a bug in > the ClojureScript implementation. >
I agree it is not a problem per se; but the feature I would really like, which I believe would require the approach I described, would be to allow the full set of Clojure constructs to be composed arbitrarily with “go”. For example a <! could live in a function, called by another function, called via a protocol, via a macro, called itself via a multi method, in another namespace, in another file, which happens to be called via a go somewhere. (And I’d like a pony.. :-) ) -- Kyle Cordes http://kylecordes.com -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
