On Thu, Nov 27, 2014 at 7:08 AM, Colin Yates <colin.ya...@gmail.com> wrote: > Mike, that's brilliant. Downloading it now.
It is a great thing to have handy, and it is also points to another example of the problem I was complaining about, which is that there are N different optimization settings, of which different tools support different subsets. Quoting the page linked, "At the time of writing, cemerick/clojurescript.test doesn't work with :optimizations :none". This is a not a great situation. We have this wonderful programming language, whose many great characteristics include a broad toolbox of mostly composable tools. But up here at the tooling level, lots of CLJS tools are not composable. -- 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 clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript.
