Channel with transducer example fails about js-csp

[rikkertkoppes]

I've been researching this a bit. It all works fine with maps, but fails with filters when they actually start filtering.

Core of the problem is that the firstgoroutine yielding on the channel put, but the value actually never gets put due to the filter. However, the goroutine is still suspended and resumes after the next successfull put (one that makes it through the filter)

Result is that the whole channel is out of sync.

No idea how to resolve it though, resuming the goroutine manually (next()) when the filter blocks seems awkward.

Maybe the solution lies in delegating the yield? (yield*) That would require rewriting channel.put and delegating the yield all the way to the adder (the transducer on the channel). That one would then yield or not.

[ubolonton]

The problem is that the reducing function add doesn't sit on the "straight-from-put-to-pending-take" path, where the buffer is not taken into account.

In core.async this was fixed by forcing all values to go through the reducing function first clojure/core.async@ad0ca86#diff-619df063e9a19af51078b3b476c49d0cL36

I still feel something is off in core.async though, specifically not being able to use transducer in a buffer-less channel.