with the flexibility and complexity that entails.
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.
// Decode on CPU
但有意思的是，在各大初创大模型企业纷纷退回到垂直领域之际，月之暗面是少数仍坚持“基座模型+Agent”路径的公司，杨植麟始终将“拿到SOTA结果”定为最重要的工作目标。