On Mon, May 4, 2015 at 10:35 AM, Jim J. Jewett wrote:
> Which reminds me ... *should* the "await" keyword work with any future,
> or is it really intentionally restricted to use with a single library
> module and 3rd party replacements?
>
You can make any Future type work with await by adding an
On Sun May 3 08:32:02 CEST 2015, Stefan Behnel wrote:
> Ok, fair enough. So, how would you use this new protocol manually then?
> Say, I already know that I won't need to await the next item that the
> iterator will return. For normal iterators, I could just call next() on it
> and continue the f
