<@U0B8FLVUH>: Well, it a bit involved, but I’ll ...
# language-proposals
a
@loganj: Well, it a bit involved, but I’ll try to explain simple smile First, async and await work in a pair: if you call await in an sync block, this block (execution context) must be stashed somewhere to free the current thread. Then, when the await-code returns, we need to reschedule the block back, and having no support from the OS (which would be native threads and is expensive anyways), we need to be able to continue executing a piece of code starting with the code right after await. When done as a library function, it is not possible, AFAIK.