await blocking.writer.write(chunk1); // ok
keyword matches.
Most userland implementations of custom ReadableStream instances do not typically bother with all the ceremony required to correctly implement both default and BYOB read support in a single stream – and for good reason. It's difficult to get right and most of the time consuming code is typically going to fallback on the default read path. The example below shows what a "correct" implementation would need to do. It's big, complex, and error prone, and not a level of complexity that the typical developer really wants to have to deal with:
比如，当用户和朋友聊到聚会要订披萨，用户可以直接叫出 Gemini，吩咐一句「弄清楚订单」，Gemini 就能直接抓取聊天中提到的披萨店，甚至特定的披萨种类，整理好每个人的需求。