With additional reporting from Mark Poynting, Jonah Fisher, Miho Tanaka and Tom Ingham.
You might assume this pattern is inherent to streaming. It isn't. The reader acquisition, the lock management, and the { value, done } protocol are all just design choices, not requirements. They are artifacts of how and when the Web streams spec was written. Async iteration exists precisely to handle sequences that arrive over time, but async iteration did not yet exist when the streams specification was written. The complexity here is pure API overhead, not fundamental necessity.
，详情可参考搜狗输入法2026
Producer: Ben Ellman
while (j = 0) {