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.
Keep up to date with the most important stories and the best deals, as picked by the PC Gamer team.
，这一点在爱思助手下载最新版本中也有详细论述
以下内容来自姚哲口述，经品牌棱镜编辑：
“功成不必在我，功成必定有我。”