Proof of concept for async pipe #252
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR creates an
async_pipe
that works with coroutines. It can be passed either synchronous or asynchronous functions as arguments, and calls them sequentially on the input, awaiting the coroutines appropriately.The
async_pipe
usesinspect.iscoroutine
to determine whether results should be awaited. An earlier version usedinspect.isawaitable
, but this did not work with the Result world, since Results are awaitable. The same would be true for Options.It also includes an extra
bind
function forasync_result
that can be used in theasync_pipeline
.I would personally find this functionality helpful for integrating with existing code that uses the standard python approach to async.