Hey,
I figured it out. Fun puzzle. ;)
As expected core.async is not the real villain here, the behavior sure is odd
but I'm not sure it is a bug.
The issue is that {:name test} inside a go block always gets turned into a
hash-map, while outside the better option array-map is chosen by the
It returns the underlying atom. The only use I can currently think of is when
you are operating with a cursor outside of the render loop and want to pull a
new cursor at a path that was nil at the time the cursor was obtained. E. g.:
(def test-cursor (om/root-cursor app-state)) ;; app-state is
I would actually consider this a core.async defect - the
interpretation of literals should not be different in go blocks. I
would open a core.async issue with all the details of this thread
summarized.
David
On Thu, Dec 25, 2014 at 12:14 PM, Sven Richter sver...@googlemail.com wrote:
Hi Thomas,
I'd imagine it becomes even less obvious once you start using your app and at
some point assoc into an array-map, getting over the threshold and turning the
result into a hash-map. I'd imagine that would be really hard to track down.
Anyways, sorted-set seems to have all sorts of caveats.
So
I like it Elyahou.
Thanks
--
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
Hi,
while I was preparing the bug report Captaion Obvious hit me again. This also
occurs in clojure:
As Thomas said, this is enough to reproduce it:
(def a (atom #{}))
(reset! a (into (sorted-set) [{:name foo}]))
(swap! a conj {:name bar})
- java.lang.ClassCastException:
Seems like a separate issue to me.
David
On Thu, Dec 25, 2014 at 3:25 PM, Sven Richter sver...@googlemail.com wrote:
Hi,
while I was preparing the bug report Captaion Obvious hit me again. This also
occurs in clojure:
As Thomas said, this is enough to reproduce it:
(def a (atom #{}))
Maps aren't comparable, so they don't make sense with sorted-set. This is
not a bug.
On Dec 25, 2014 12:25 PM, Sven Richter sver...@googlemail.com wrote:
Hi,
while I was preparing the bug report Captaion Obvious hit me again. This
also occurs in clojure:
As Thomas said, this is enough to
Hello Andrew,
I'd like to be able to run my cljs test on a continuous integration server.
For that purpose. I need to get a proper exit code from lein cljsbuild once
test
With your tutorial,
lein cljsbuild once test always return 0.
Is there a way to make the build fail when the tests fail?
Hi Arnaud,
I feel your pain. I've been developing with cljs nearly from the beginning
(though as a newbie to Clojure) and the road has been bumpy but plenty
rewarding. My advice is to stay at it; your flow will improve and the language
and tooling have been improving a lot, too.
I'll speak to
10 matches
Mail list logo
