Lowest danger rate
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中也有详细论述
"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 Version/17.0 Safari/605.1.15",
Google 将 AppFunctions 类比为 Android 的「模型上下文协议」（MCP），可以简单理解为一个对话标准，帮助第三方的 App 应用和 AI 模型进行对接。