Fork me on GitHub

is there a reason merge doesn't take a transducer?


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.

Alex Miller (Clojure team)14:05:25

well the common way is to optionally supply the output channel isn’t it?

Alex Miller (Clojure team)14:05:00

seems like merge could take buff-or-n-or-channel