FromIterator<F> for Unicycle<F> would be more ergonomic

[dekellum]

I tested one case, and I suspect it will be a common pattern for users to want to drop in Unicycle where FuturesUnordered was previously used. The Unicyle would have been a drop in replacement if it implemented FromIterator like FuturesUnordered does, allowing it to be assembled via std::iter::Iterator::collect.

[udoprog]

Thanks for the report!
I've added naive implementations for Collect in master at the moment.

They could be improved to take [Iterator::size_hint] into account to pre-allocate the collections used, so I've opened #3 to track this.

[BlinkyStitt]

Can you share an example of using this? Thanks!

[udoprog]

Hey @wysenynja

I added an example here: https://github.com/udoprog/unicycle/blob/master/src/lib.rs#L54

Does that help?

[BlinkyStitt]

Yes. Thank you!

…

On Mar 17, 2020, at 9:31 PM, John-John Tedro ***@***.***> wrote: Hey @wysenynja <https://github.com/WyseNynja> I added an example here: https://github.com/udoprog/unicycle/blob/master/src/lib.rs#L54 <https://github.com/udoprog/unicycle/blob/master/src/lib.rs#L54> Does that help? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEYMXLVVHUCEGB4Y4S7MJTRIBFDVANCNFSM4KN5SNCQ>.