This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-01
Channels
- # announcements (3)
- # beginners (59)
- # calva (23)
- # cider (58)
- # clojure (125)
- # clojure-dev (18)
- # clojure-dusseldorf (1)
- # clojure-europe (21)
- # clojure-germany (1)
- # clojure-hamburg (1)
- # clojure-italy (13)
- # clojure-nl (29)
- # clojure-poland (3)
- # clojure-spec (61)
- # clojure-uk (74)
- # clojurescript (12)
- # core-async (6)
- # cursive (4)
- # data-science (7)
- # datomic (14)
- # defnpodcast (1)
- # events (4)
- # fulcro (72)
- # juxt (36)
- # kaocha (3)
- # nginx (3)
- # off-topic (14)
- # pathom (5)
- # ring-swagger (68)
- # shadow-cljs (25)
- # spacemacs (8)
- # sql (42)
- # tools-deps (8)
- # vim (6)
@idiomancy it's not the case of use a transducer on channel?
as is frequently the case with core.async, I ended up completely rethinking my approach
Oh no!!
I saw mix, and I thought it was like the inverse of mult, like,
"put value on out-chan when and only when a value has been consumed from each of the inputs"
like, I thought if there was
(toggle (mix out) {in1 {} in2 {}})
that takes to out
would park until a put to both in1
and in2
had occurred
@idiomancy wouldn't (async/map f in1 in2)
do this - calling f
for each pair of values from in1 / in2 and always waiting for both?