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.
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"?