- From: Adam Rice <notifications@github.com>
- Date: Mon, 23 Apr 2018 03:34:00 +0000 (UTC)
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 23 April 2018 03:34:27 UTC
If in future we'd like TextEncoderStream's `readable` side to be a byte stream then we have a conflict here. It's undesirable for user code to be able to view the encode in progress, because it may be using vector ops or other things that are browser-specific. There are probably going to be other cases of platform streams where we'd like to prevent intermediate values from being visible. I think all solutions involve adding an extra copy when the output is a SharedArrayBuffer. The question is whether this copy becomes part of the ReadableStream machinery that is specified by a flag, or whether the underlying source has to detect that `controller.byobRequest.view` is an SAB and do the copy itself. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/streams/issues/757#issuecomment-383445030
Received on Monday, 23 April 2018 03:34:27 UTC