Async-await on stable Rust!

Sebastiaan Koppe mail at
Fri Nov 8 15:11:27 UTC 2019

On Friday, 8 November 2019 at 14:28:36 UTC, rikki cattermole 
> On 09/11/2019 2:24 AM, Sebastiaan Koppe wrote:
>> What does 'ready to execute' mean? And why synchronously? 
>> isn't the idea of async to run concurrently?
> So ready to execute could mean that a socket has data in the 
> buffer ready to be read.

Ah, you mean after it first yielded.

> In other words, I don't want this behavior baked into the 
> language. That seems like a good way to have regrets that we 
> can't fix easily.

I am not so sure, good concurrency seems to require a little help 
from the compiler.

> Indeed that was a very simple example. But throw in a copy 
> constructor + destructor pair, you should be able to build up a 
> nice little tree on the Nursery implementation instance. Which 
> from what I read could be quite useful with executing the 
> closures.


More information about the Digitalmars-d mailing list