I'm fine with the body overloading.
IIUC no more overloading will be introduced: With streams, we will prefer
encoders / decoders integrated with streams more than adding overloads to
APIs, in order to support new types. So it is acceptable to add the last
overload here I think.
Thanks,
On Wed,
In https://github.com/yutakahirano/fetch-with-streams Yutaka, Anne, and I are
working on how to integrate the fetch API with streams. The general pattern we
want is that for both request and response objects their creator is given a
writable stream to write body content to, using [the revealing
