`await promise` does not guarantee the yield of control flow about deno HOT 3 CLOSED

In browsers, an await operation queues a microtask when the promise resolves to continue execution, while a setTimeout call queues a task after some time to invoke the callback. Microtasks have a higher priority than tasks. That is, the event loop first runs every microtask before moving on to the next task. You can read more about the event loop on MDN.

Deno tries to follow browser behavior as far as possible. In your code, the microtask enqueued by every await operation immediately executes another await operation, so there is always a microtask in the queue, and the next task is never visited.

from deno.

@0f-0b You are amazing! It helped me a lot!

from deno.

Yup, @0f-0b answered this perfectly. This is the way Promises work in JS.

from deno.