This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-10-10
Channels
- # announcements (1)
- # asami (36)
- # babashka-sci-dev (5)
- # beginners (4)
- # calva (10)
- # chlorine-clover (2)
- # clj-commons (2)
- # clojure (35)
- # clojure-android (1)
- # clojure-norway (1)
- # clojurescript (11)
- # cursive (8)
- # deps-new (5)
- # emacs (8)
- # fulcro (11)
- # graalvm (15)
- # gratitude (5)
- # holy-lambda (11)
- # jobs-discuss (5)
- # lsp (9)
- # off-topic (9)
- # other-languages (2)
- # pathom (6)
- # polylith (43)
- # portal (35)
- # quil (6)
- # react (13)
- # reclojure (3)
- # releases (5)
- # rewrite-clj (13)
- # shadow-cljs (32)
Am I missing something?!
Whatever I try, .push
on JS arr
seems to be ignored in a goroutine when the array is created in that goroutine. E.g. following prints only #js [1]
(async/go
(let [arr #js [1]]
(.push arr 2)
(println arr)))
I suspects it is indeed about the tag but yet I can't understand what's going on because arr
is indeed a JS array.
When I print the type and all, I mean. It's not like tag is ignored for instance.
Trying to understand it would require going through the broken code of core.async
. No reason to do that when you know how to not trigger its bad behavior, and IIRC David either plans to work or is already working on it.
Yep. For context, I get that kind of problems with arrays but not objects.
So anyways, this is known? I shouldn't report it anywhere?
As I said - @U050B88UR knows about it and either is working or plans to work on it, as he himself mentioned not so long ago.