Adam Rice

@MattiasBuelens How hard would it be to just add an optional second argument to `fill()`?

> Looks reasonable so far. Should we make unbuffered transforms the default? I suspect it's more desirable, and hopefully wouldn't be too breaking... I'm concerned that people may be relying...

I haven't had a chance to look at the implementation in detail. I think Chrome is interested in this functionality in general. I will leave it to @domenic to make...

> > * Store the previous chunk, and enqueue it when branch 2 (eventually) starts pulling. This chunk can be overwritten when branch 1 pulls in more chunks in the...

I've been having second thoughts about this. But I really want to provide a stable target in the medium-term for browsers to implement. We could probably keep tweaking things forever...

It would be nice to have a description of the concept from the developer's perspective, too.

My impression is that the `write()` method is more focussed on providing features that are not available in in the WritableStreamDefaultWriter `write()` method, rather than convenience.

What does the markup look like? I'm worried that the source could end up unreadable if we do this.

I'm in favour.

Maybe the solution is simply to declare that a specific set of platform streams are "fully detachable" and standardise their behaviour explicitly? I was hoping to make optimisation transparent to...