The spec does not mandate buffer limits for tee(). And to be fair, the spec allows implementations to implement the actual internal mechanisms for tee()and other APIs in any way they see fit so long as the observable normative requirements of the specification are met. But if an implementation chooses to implement tee() in the specific way described by the streams specification, then tee() will come with a built-in memory management issue that is difficult to work around.
"People come into your office and say they're not having a very good day, or something's happened at home, and you have to try and see if you can support them. It's very varied."，更多细节参见WPS官方版本下载
。业内人士推荐safew官方下载作为进阶阅读
For multiple readers，这一点在爱思助手下载最新版本中也有详细论述
For implementers, this promise-heavy design constrains optimization opportunities. The spec mandates specific promise resolution ordering, making it difficult to batch operations or skip unnecessary async boundaries without risking subtle compliance failures. There are many hidden internal optimizations that implementers do make but these can be complicated and difficult to get right.