Taiki Endo

Closing in favor of existing issue/pr.

Except that the behavior of the `None` case is different from the existing `OptionFuture` (and https://github.com/rust-lang/libs-team/issues/197), I think this is reasonable.

Thanks for the PR! `size_hint` means the number of elements remaining in the entire stream, and since the information we really want here is the number of elements until the...

> reuse it on every entry to poll_next? How to reuse it? poll_next returns an owned Vec.

> Can't we return a reference to the internal vector? > make Self::Item be a `& Vec` ? I don't think it is possible without using GAT in the Future...

Hmm. The current one is correct for the `futures` documentation, but indeed incorrect for the `futures-util` documentation. https://github.com/rust-lang/futures-rs/blob/ae3297f25d4bc26e000990cc1dfd16505ae9998a/futures-util/Cargo.toml#L17-L18 https://github.com/rust-lang/futures-rs/blob/ae3297f25d4bc26e000990cc1dfd16505ae9998a/futures/Cargo.toml#L39 0.4 should fix the difference here (https://github.com/rust-lang/futures-rs/issues/2308#issuecomment-778572610, https://github.com/rust-lang/futures-rs/issues/2295), but it is...

Closing -- as said above, 0.3 requires a more complex fix and 0.4 does not need to do anything. In any case, this PR will not work as a corrective...

I think this could cause breakage if a different method with the same name as a method in std::io traits is added to futures::io traits.

Closing this due to the above concern. Thanks anyway for the PR!

Given that `SpawnExt` requires alloc, I don't think there is much benefit to use `Spawn` trait in a no-alloc environment. (Perhaps it more makes sense to add something like tokio...