for await...of sequential execution limits with async iterators
Designing a streaming pipeline that consumes an async iterable with for await...of raises questions about execution guarantees and resource cleanup. The documented behavior is sequential pause at each yield point until the promise from next() resolves, with no parallel iteration unless explicitly composed. A specific concern is the interaction with synchrono
javascript