SE-0300 (Second review): Continuations for interfacing async tasks with synchronous code

[Joe_Groff]

@Lantua

Just to clarify, the task (may) suspend at the end of operation , and it resumes after resume is call or operation finishes whichever comes later , right? Given that operation is called using the task context, we can't have them resumed when it is still running, esp. in case we use concurrent/custom executors.

The task always suspends until resume is called. Once operation returns, the task stops executing, and the executor is free to schedule another task on the same thread.

@Lantua

I don't remember if this has been brought up before, but I think this would be the first unsafe function when its meaning is outside of memory safety. Are we embracing a broader meaning of unsafe or should we add another "keyword"?

It is absolutely memory-unsafe to misuse a continuation.