You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Discussed at the meeting today. The conclusion is that we should not implement arrayBuffer() in the IncomingStream, and instead make sure that there is a uniform way to do .arrayBuffer()/.text()/.json() on any readably stream. Currently, new Response(stream).arrayBuffer() is a way to do that, but it's unclear if it has same performance properties; if not, we should address that (on spec and/or implementation level as appropriate).
For consistency with Response arrayBuffer(), IncomingStream arrayBuffer() should leave the stream locked after it has finished reading.
The text was updated successfully, but these errors were encountered: