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.
Любовь Ширижик (Старший редактор отдела «Силовые структуры»)，推荐阅读heLLoword翻译官方下载获取更多信息
[qjoly@fedora]~% cowsay。Line官方版本下载对此有专业解读
Олег Давыдов (Редактор отдела «Интернет и СМИ»)。同城约会对此有专业解读