Matthew Gaudet

(this might just be echoing @ricea above) I think this bug is even more general: I've got a prototype implementation of streams that uses the promise semantics, and [even without...

So I just want to clarify the state of the world here, so I'm sure. The original issue (https://github.com/whatwg/streams/issues/933) was that the internals of `pipeTo` were visible. However, as Dominic...

I apologize for the game of telephone that's been going on (I'll partially blame timezones here). So, here's my take on this. I'm implementing ReadableStreams in Firefox using DOM technologies...

> The last step you mention (resolving a promise) should not happen if you're using ReadableStreamDefaultReaderRead. That's only part of ReadableStreamDefaultReader.read(). A-Hah! You spotted (what is almost certainly) the [bug...

Gecko has the same story: Calling convention changes for throwing algorithms, and places where we will throw that the specification says has throwing impossible. Minimizing these cases is on my...

I guess one thing I don't quite understand is the structure of the proposed headers. You're suggesting something like > **SetUpWritableStreamDefaultController(stream, controller, startAlgorithm, writeAlgorithm, closeAlgorithm, abortAlgorithm, highWaterMark, sizeAlgorithm)** performs the...

Just to weigh in here: I think we (Mozilla) are generally supportive of the proposal; it's a great user feature. I did a scan of the specification today, and while...

So, just to clarify what ellisp meant for future Googlers like myself, from my reverse engineering of his comment: You can correct the spaces problem, even for PDF output, by...

Yeah, this is for sure something I struggled with. It's hard to document the bounds directly, as they're gut-driven, but the project would certainly benefit from me writing down some...

HDL/Synthesis compilers are definitely in scope: never heard of blue spec, but if you could add them that would certainly be great if they apply.