Re: core.async pub/sub closing source channel issue

The reason for the behavior you are observing is a race condition. The effects of close! on the pub aren't synchronous. Even though the channel is immediately closed before return, consumers need time to determine that it has been closed. At the point in time the pub determines that the source

Re: core.async pub/sub

not sure when then added this but it looks like pub and sub are in the async lib now. any differences between what they have now and what you need? looking for some examp

Re: core.async pub/sub

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

Re: core.async pub/sub

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