channels to be closed as a consequence of closing the source channel.
On Sunday, March 1, 2015 at 2:17:20 PM UTC+1, Jonas wrote:
Hi all!
I’m working with core.async pub/sub and ran into an issue which I don’t
quite understand. According to the clojure.core.async/sub docstring:
By default
Hi all!
I’m working with core.async pub/sub and ran into an issue which I don’t
quite understand. According to the clojure.core.async/sub docstring:
By default the channel will be closed when the source closes
This is not the behaviour I’m seeing when I call
clojure.core.async/unsub-all
not sure when then added this but it looks like
pubhttp://clojure.github.io/core.async/#clojure.core.async/pub
and sub http://clojure.github.io/core.async/#clojure.core.async/sub are
in the async lib now.
any differences between what they have now and what you need?
looking for some example
Hey,
the lab stuff looks very interesting, I however couldn't quite figure out
how to unsubscribe one channel from the broadcast since I cannot exchange
the topic for every subscriber when one subscriber decides to leave. Its
also a lot lower level than I'm currently comfortable with since I
There is a broadcast fn in the lab namespace
(https://github.com/clojure/core.async/blob/master/src/main/clojure/clojure/core/async/lab.clj)
that does this and I believe David Nolen has created a different variant in
some of his stuff. The lab one is experimental and would welcome feedback
on
Hey,
I'm doing some core.async tests and want to create a basic pub/sub model.
Messages are ! on one channel and ! to many others.
(deftest ^:wip async-test2
(let [subscribers (atom [])
events (chan 100)]
(go (loop []
(when-let [ev (! events)]
(doseq [c
