Re: Design consideration: when are pipe objects enabled with the benefits of decoupling?
Does a series of yields still exploit the benefits of decoupling? (e.g., independently able to stop the stream) - E
On Sunday, February 26, 2017 at 3:50:40 PM UTC-5, Gabriel Gonzalez wrote:
B might sometimes be faster than A because `(~>)` is easier to optimize than `(>->)`
If presented with the following design choices:
A. getRecords h >-> parsePipe >-> P.print
...where the getRecords both awaits and yields
B. ( (a -> m b) ~> (b -> m c) ) h >-> P.print
... where each of the kleisli arrows yields
Does A have 2 decoupled points
#1. between getRecords h >-> and parsePipe
#2. between parsePipe and P.print's
Versus B only one between the final yield from the second k :: (b -> m c) and the await from P.print?