Provide paginators interop with the futures::Stream
implementation
#1028
Labels
feature-request
A feature should be added or improved.
p2
This is a standard priority issue
pending-release
This issue will be fixed by an approved PR that hasn't been released yet.
Describe the feature
The removal of
futures::Stream
implementation in1.0
for paginators is a breaking change for lots of our code (both public: elastio/ssstar#125 and private).Consider implementing
futures::Stream
for paginators again either:feature = "futures"
futures::Stream
implementor newtype. For example, like conversion of timestamps tochrono
is implemented inaws_smithy_types_convert
crate. This is the least-preferred variant, because we'll still need to explicitly import some extension trait and call.into_stream()
or smth like that to use the paginator as afutures::Stream
.Basically, we need a shared interop code so that we don't have to write this boilerplate newtype wrapper over and over again in various places. Have a shared interop code that everyone in the open-source community can use.
Use Case
futures::Stream
contains a lot of useful combinators with[Try]StreamExt
traits and also a lot of our code works withimpl futures::Stream
. It's basically the golden standard akin toIterator
in the ecosystem and we've been using it everywhere including with the pre-1.0 AWS SDK code.A note for the community
Community Note
The text was updated successfully, but these errors were encountered: