Hey Moe,
>
>>
>> into and pipe should probably be safe.
>
>
> I was thinking of a case where a function is returning the equivalent of:
>
> (async/onto-chan ... [1 2 (Exception.)])
>
> And the consumer wants to async/into [], obscuring the error from looks like you've defined <
> I have som
Hi Moe,
>
> I haven't felt the need for Erlang-style supervision in core.async,
> but am generally interested in moving around errors
> asynchronously.
>
> How are you dealing with failures which pass through higher-order
> channel operations, e.g. into, map, pipe, etc.?
into and pipe should pr