Re: [whatwg/encoding] Add support for [AllowResizable] inputs (Issue #344)

annevk left a comment (whatwg/encoding#344)

That's strange, neither link 404s for me.

- I think allowing this for `decode()` is straightforward and something we should do. It makes a copy (that could be optimized) so it doesn't really matter if the underlying buffer can change in size.
- I think the same applies to `TextDecoderStream`. "decode and enqueue a chunk" makes a copy (that could be optimized) so it doesn't really matter if the underlying buffer can change in size.
- For `encodeInto()` it's a bit less clear. Should the API attempt to grow the buffer if the input doesn't fit, for instance? And can the write be atomic so it doesn't grow or shrink at the same time we are writing into it?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/344#issuecomment-2827266142
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/encoding/issues/344/2827266142@github.com>