This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-05-07
Channels
- # aleph (8)
- # beginners (16)
- # boot (5)
- # cider (22)
- # cljs-dev (15)
- # clojars (10)
- # clojure (94)
- # clojure-dusseldorf (1)
- # clojure-france (57)
- # clojure-greece (1)
- # clojure-spec (9)
- # clojurescript (15)
- # core-async (6)
- # cursive (11)
- # datomic (10)
- # emacs (6)
- # funcool (1)
- # hoplon (1)
- # off-topic (5)
- # re-frame (8)
- # spacemacs (8)
- # specter (4)
- # unrepl (10)
- # vim (5)
it's older than transducers, I guess core.async/merge could be extended to take a transducer arg, sounds like a good pull request
@noisesmith I'm playing around with that and seems to work fine so far 🙂
So the biggest issue to a patch for this getting accepted (in my opinion) is that it wouldn't go far enough. What you're discussing is how to configure the output channel of merge
. But there are other options to channels as well (for example, exception handlers) so the question is, do we want (merge chaos buff-or-n xf ex-handler)
and do we want that on every core.async function that creates a channel? If we do, we probably want to find a generic and uniform way to do it for all core.async functions.
well the common way is to optionally supply the output channel isn’t it?
seems like merge could take buff-or-n-or-channel