On Tuesday, 10 March 2015 09:41:45 UTC+10, David Nolen wrote:
ClojureScript, the Clojure compiler that emits JavaScript source code.
New release version: 0.0-3058
The new Quick Start is essential reading even if you are a relatively
experienced ClojureScript developer.
I did this, and
On Wednesday, 11 March 2015 23:38:40 UTC+10, Peter West wrote:
On Tuesday, 10 March 2015 09:41:45 UTC+10, David Nolen wrote:
ClojureScript, the Clojure compiler that emits JavaScript source code.
New release version: 0.0-3058
The new Quick Start is essential reading even if you are
It seems that (doc ...) and (source ...) do not print any text
after (require '[hello-world.core :as hello] :reload) has been entered at
the (browser) REPL.
On Monday, March 9, 2015 at 7:42:28 PM UTC-4, David Nolen wrote:
ClojureScript, the Clojure compiler that emits JavaScript source code.
It's no more or less difficult than using Clojure by itself. You can use
whatever tool you want to manage dependencies.
That said I would probably use Maven or Lein myself. Using Maven directly
with AOTed dependencies will likely result in a fast workflow. AOTed
tools.reader and data.json JARs
A couple of people mentioned this happened while trying out the Quick
Start. If eval takes a long time it could be because you don't have the
right browser tab focused. If the REPL is truly hung due to some kind of
communication issue, try refreshing the browser. The bREPL uses an iframe
which can
Amazing update! Yay.
But I just spotted one weird thing, after I pumped compiler version compilation
fails for me with following error:
clojure.lang.ExceptionInfo: failed compiling
file:public/javascripts/out-server-side/cljs/core.cljs {:file #File
Looks like you're trying to use :cache-analysis with a higher
:optimizations setting than :none. I would avoid this for now.
http://dev.clojure.org/jira/browse/CLJS-1103
David
On Tue, Mar 10, 2015 at 6:07 AM, Max Gonzih gon...@gmail.com wrote:
Amazing update! Yay.
But I just spotted one
On Tuesday, 10 March 2015 10:55:49 UTC, David Nolen wrote:
Looks like you're trying to use :cache-analysis with a higher :optimizations
setting than :none. I would avoid this for now.
That fixed the same problem for me. Thanks.
Also my cold compile time went down from 40s to 25s!
Thanks,
Hopefully we can get that down 1s for anything except production builds.
Next on the list of todos is a shared AOT cache for all projects builds.
Once you've compiled a dependency from a JAR we should never compile it
ever again.
On Tue, Mar 10, 2015 at 9:11 AM, Chris McDevitt
Thanks David, it solved my problem!
--
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
This is great, David!
Is it difficult to include dependencies (e.g., core.async) for a project built
this way?
--
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
It says analysis caching is enabled when optimizations is :none. Do we have
to enable to explicitly on other optimization levels?
tirsdag 10. mars 2015 00.42.28 UTC+1 skrev David Nolen følgende:
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code:
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-3058
Leiningen dependency information:
[org.clojure/clojurescript 0.0-3058]
This is a significant enhancement release around
Just wow! Thank you.
On Tuesday, March 10, 2015 at 12:41:45 AM UTC+1, David Nolen wrote:
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-3058
Leiningen dependency
14 matches
Mail list logo
