This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-31
Channels
- # aleph (38)
- # beginners (91)
- # boot (4)
- # cider (20)
- # clara (11)
- # cljs-dev (4)
- # clojure (179)
- # clojure-greece (1)
- # clojure-italy (16)
- # clojure-portugal (1)
- # clojure-russia (1)
- # clojure-sanfrancisco (1)
- # clojure-spec (183)
- # clojure-uk (50)
- # clojurescript (111)
- # core-async (24)
- # cursive (4)
- # datascript (11)
- # datomic (29)
- # fulcro (120)
- # gorilla (2)
- # jobs (1)
- # keechma (2)
- # keyboards (26)
- # leiningen (4)
- # luminus (7)
- # lumo (15)
- # off-topic (2)
- # onyx (31)
- # parinfer (12)
- # portkey (1)
- # protorepl (1)
- # re-frame (50)
- # reagent (106)
- # remote-jobs (1)
- # ring-swagger (2)
- # rum (10)
- # spacemacs (17)
- # sql (16)
- # test-check (1)
- # yada (2)
Question: is (binding) going to behave like I think it should when I’m using go blocks?
hahaha
yeah, I’m not in clojurescript
but I was using binding
to re-route println to a different writer
but things ended up going to stdout anyway
so I was just checking to see if “everybody knows that you shouldn’t use binding
in go blocks!”
because every now and then, I make those kinds of mistakes
go blocks carry the bindings from outside the block
like, if you bind out around the creating of the go block, then for the duration of that go block, unless the go block changes it, code in the go block will see the value you bound for out
okay, but if I bind inside of the go block …
it works fine as well, just tried it
it’s also possible that I’m in the fog of post-lunch needing a nap 😄
so the binding machinery works fine, but if you are initing the binding from another thread local, etc, things can end up not working as expected
@hiredman example of that?
It should work exactly like bindings with future