reading through whatwg @streamsstandard to update myself on its latest state — I have to say, I haven't seen anything disagreeable!
-
put another way, Node streams expose an API that is half private and half public, and which half is which depends on how the stream is used
-
-
@yoshuawuyts streams2+ doesn't address the problem. If one has piped, one shouldn't call .read, .write, or .end, or emit certain events. -
@yoshuawuyts (but if you're talking the WHATWG ReadableStreamReader + locking a ReadableStream for reading, yep! — that solves the problem) - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.