Michal Kawalec

@dougwilson @brian-learningpool rereview please

Will rebase soon, hopefully we'll get this across the finish line in 2019 :D

Hey @arlyon! A `Stream` would only give out a single evaluated element at a time (see the `poll_next` method [on the `Stream`](https://docs.rs/futures/latest/futures/stream/trait.Stream.html)). This means that it's construction itself blocks us...

Good idea, I'll add something similar to the todolist, that converts a `Stream` into a `Deluge` without materializing the whole intermediate dataset. Of course you are encouraged to contribute it...

Closing because I don't believe there is a straightforward way to convert a stream into a `Deluge` given that a `Deluge` needs to know how many elements it is going...

I just realized I can use [`StreamExt::chunks`](https://docs.rs/futures/latest/futures/stream/trait.StreamExt.html#method.chunks) for this exact purpose, hiding it behind a conversion api :D

@lemol, @jtdaugherty This performance issue is probably related to the fact that even the ByteString implementations use a String fetcher. Would you be willing to accept PRs that fix that?

@lemol: Decided to go the long way and created my own imap library, https://github.com/mkawalec/imap.

This looks deceptively simple. I don't have much time on my hands either, but I would also want this implemented. @staltz do you know of a good testing PoC to...

I think https://github.com/infinyon/node-bindgen/pull/155 simplifies the issues @NovaLogicDev has had - now structs and enums to-js conversions can be autoderived. Also structured errors can be returned from `Result`, so something like...