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.
The hidden cost of promises
，详情可参考WPS官方版本下载
One day, I will start my last project. I may or may not finish it. But after it's done, either due to tragedy, falling out of love with the craft, or simply not having time left to start another one, I will put my computer and notebooks down for the last time. That's life.
The world stopped breathing and watched.