- From: Joshua Bell <notifications@github.com>
- Date: Tue, 29 Jun 2021 16:05:41 -0700
- To: whatwg/encoding <encoding@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 29 June 2021 23:05:54 UTC
It's unclear what the benefit of the proposed change is. It doesn't save significant typing (just `new`); in cases where you want to avoid allocating a new instance, the encoder/decoder can be cached and used statelessly. Given a time machine to redesign the API now that streams are a thing, this makes more sense for non-streaming encodes/decodes, but is it worth adding to the platform? -- 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/encoding/issues/267#issuecomment-870974914
Received on Tuesday, 29 June 2021 23:05:54 UTC