I am confused by the interleaving of the [:x _] and [:y _] tap> output with the [:a _] and [:b _] output in https://gist.github.com/telekid/67ae7b3bd066aa346877d3bad6eb76fb.
It looks arbitrary to me (which I can get behind given that it's in an m/ap body) but just want to make sure I'm not missing something.
The ordering you observe is a consequence of both 1- ap backpressure (well defined) and 2- ap buffering strategy (currently undefined, but will eventually be).
In the current implementation there is too much buffering, ap evaluates more eagerly than it should
There are good reasons why ap evaluation model should be well defined, ticket here https://github.com/leonoel/missionary/issues/109
Cool, got it. Thanks Leo!
https://gist.github.com/telekid/38c313e87fc2459f3f137dd64d307157#file-example-clj-L74-L87
It's not The problem here is accept calls not properly serialized