I can't get core.async working with 0.0-1877+: nothing is executed in go block
without any warnings and errors. When I use 0.0-1859 everything goes fine.
(I've surely done lein cljsbuild clean)
--
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To
This release seemed to introduce a subtle bug with (clj->js ...) in advanced
compilation. Here is the demo project (https://github.com/MarcoPolo/test-cljs).
If you run (lein cljsbuild clean && lein cljsbuild auto) and use lein
trampoline repl-listen (just for the webserver), the first compilatio
I am using 1889. Since the update, my keywords are getting printed as #<[object
Object]> How do I print a keyword now?
On Wednesday, September 11, 2013 11:09:29 PM UTC-4, David Nolen wrote:
> 1878 went out today, the only change was fixing a bug introduced by 1877 that
> caused spurious warnin
1878 went out today, the only change was fixing a bug introduced by 1877
that caused spurious warnings when incrementally compiling.
On Mon, Sep 9, 2013 at 9:50 PM, Brandon Bloom wrote:
> > a (very) temporary workaround is to use the old code
>
> Why not just switch (k coll) to (get coll k) ?
>
> a (very) temporary workaround is to use the old code
Why not just switch (k coll) to (get coll k) ?
If you know that coll is non-nil, you can also just use (coll k). Both
forms also accept an optional not-found value.
--
--
You received this message because you are subscribed to the Google
Can't have thoughts without a lot more details :) Specific errors,
warnings, and a minimal case is always ideal.
David
On Mon, Sep 9, 2013 at 12:04 PM, wrote:
> A large percentage of tests for my core.async based library are failing.
> Any thoughts?
>
> --
> Note that posts from new members a
A large percentage of tests for my core.async based library are failing. Any
thoughts?
--
--
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 -
Also, a warning about breaking change with the strings no longer being
keywords:
Previously in ClojureScript, strings could be invoked to look themselves up
as keys inside maps, just like keywords. So both (:a {:a 10 "b" 20}) and
("b" {:a 10 "b" 20}) would work (the latter will not work in vanilla
Are you trying that with an existing project that may have a stale target
directory lying around? If you can reproduce this issue after a `lein
cljsbuild clean` then yes please open a ticket with a minimal project that
exhibits the issue.
Thanks!
David
On Mon, Sep 9, 2013 at 9:18 AM, Julien Elua
On Sun, Sep 8, 2013 at 7:42 PM, 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-1877
>
> Leiningen dependency information:
>
> [org.clojure/clojurescrip
I'm getting the same long list of warnings as Julien
--
--
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
Hi David,
that is really nice! Speedup during incremental build is definitively the one
thing that would improve my ClojureScript dev workflow.
I gave this build a try with lein-cljsbuild and got some unexpected WARNINGS.
What I am doing:
* lein cljsbuild once => everything is fine
* change som
ClojureScript, the Clojure compiler that emits JavaScript source code.
README and source code: https://github.com/clojure/clojurescript
New release version: 0.0-1877
Leiningen dependency information:
[org.clojure/clojurescript "0.0-1877"]
*Breaking Changes: *
* Keywords are no longer repre
13 matches
Mail list logo
