feat: Expose poll_next_field so it can be used by frameworks that use pure Futures #50
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.
Ok, here I come again with the crazy ideas :D
While implementing multer on warp (seanmonstar/warp#1033) I saw that you already have a polling function for the next item, and it would be useful to have a clean implementation on warp without resorting to stream::unfold and whatnot.
Is that a feasible change to be merged?