On Tuesday, December 18, 2012 1:02:55 AM UTC-5, Mikera wrote:
>
> Re: tools.namespace, I've found some similar functions in the bultitude
> library (https://github.com/Raynes/bultitude/tree/master/src/bultitude).
> Apparently it addresses
> "specific needs that clojure.tools.namespace did not pr
Actually, scratch that first one. Looks like Stuart did finally apply the
patch. Other reasons for bultitude's existence still apply.
On Tuesday, December 18, 2012 6:06:40 AM UTC-6, Anthony Grimes wrote:
>
> http://dev.clojure.org/jira/browse/TNS-1 is the reason why I did
> bultitude. It was an
http://dev.clojure.org/jira/browse/TNS-1 is the reason why I did bultitude.
It was an important bug that was never addressed, and probably still hasn't
been addressed. Other people have also added relatively complex classpath
features to it as well, and since it isn't a contrib project you can
Hi Stuart,
Re: tools.namespace, I've found some similar functions in the bultitude
library (https://github.com/Raynes/bultitude/tree/master/src/bultitude).
Apparently it addresses
"specific needs that clojure.tools.namespace did not provide".
Is one of these recommended over the other, or is t
FrankS wrote:
> Does Flow work with ClojureScript?
I haven't tried. In principle, there's no reason why it
couldn't. It uses macros, so it would require some porting.
> It feels like expressing and using those Flows could solve
> similar call-back-hell problem in the single-threaded
> asynchronou
Does Flow work with ClojureScript?
It feels like expressing and using those Flows could solve similar
call-back-hell problem in the single-threaded asynchronous javascript world,
and could be an alternative to promises (?).
(hopefully I understood the functionality well after a quick scan and g
