v1.0.0#specification reads:
> Or another implementation could fuse the operations to the final consumer:
> nioSelectorThreadOrigin | map(f) filter(p) consumeTo(toNioSelectorOutput)
Having control over how to fuse a chain of functions is very interesting. Do any of the implementations allow use of mutable state when fusing a chain of functions with the same signature.
Comments
v1.0.0#specification reads: > Or another implementation could fuse the operations to the final consumer: > nioSelectorThreadOrigin | map(f) filter(p) consumeTo(toNioSelectorOutput)
Having control over how to fuse a chain of functions is very interesting. Do any of the implementations allow use of mutable state when fusing a chain of functions with the same signature.