This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-19
Channels
- # beginners (69)
- # boot (10)
- # cider (18)
- # cljsrn (6)
- # clojure (225)
- # clojure-austin (1)
- # clojure-dusseldorf (7)
- # clojure-france (2)
- # clojure-greece (3)
- # clojure-italy (9)
- # clojure-madison (6)
- # clojure-miami (1)
- # clojure-mke (2)
- # clojure-russia (58)
- # clojure-sg (36)
- # clojure-spec (25)
- # clojure-uk (54)
- # clojurescript (20)
- # core-async (15)
- # cursive (16)
- # datomic (71)
- # emacs (7)
- # hoplon (3)
- # jobs (5)
- # jobs-discuss (4)
- # klipse (3)
- # leiningen (2)
- # lumo (60)
- # mount (1)
- # off-topic (16)
- # om (6)
- # om-next (7)
- # onyx (21)
- # pedestal (15)
- # planck (1)
- # re-frame (3)
- # ring-swagger (4)
- # specter (33)
- # uncomplicate (31)
- # untangled (8)
- # vim (35)
Hi,
about core.async/thread
: is the code running in a core.async thread or a JVM thread?
Is there a way to subscribe to all the topics of a pub
@viebel interesting question - if I was doing that I would make a mult
then create two tap
instances of the mult
, one of which becomes the pub
the other you listen to directly - but I'm not sure that's the simplest answer (it would work though)
A bit complicated @noisesmith
If there is no simple way to do it in core.async
, there is probably a good reason
right, I assume there's something simpler
really what you want is both fan out and fan in, but it's simpler to capture the messages before the fan out and use that as your fan-in
I'd disagree regarding "probably a good reason". These are conveniences and none of the operations describe contradict good core.async usage.
I'd welcome an explanation of why I'm wrong though - not an expert on this aspect of core.async, just trying to help as much as I can.
That's the best way to do it I'd say
Also, I would argue that this is indeed simple in the sense of composing complex behavior from simple parts 🙂