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.
Материалы по теме:
，更多细节参见快连下载安装
第一节 扰乱公共秩序的行为和处罚
Овечкин продлил безголевую серию в составе Вашингтона09:40