await dropNew.writer.write(chunk3); // silently dropped
processAll(tasks)
，这一点在51吃瓜中也有详细论述
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.
The tone checker, is a great feature that helps you ensure that your content is consistent with your brand’s voice. This is excellent for crafting cohesive and on-brand content.