Re: [whatwg/encoding] Add a static decode and encode method to `TextEncoder` and `TextDecoder` (#267)

If we add API surface that doesn't work in old browsers, I'd like to know if users of the potential API surface care about non-UTF-8 encodings. If not, I'd prefer adding new API surface to JavaScript `String` itself instead of `TextDecoder`, since the WebIDL layer is a perf bottle neck.

* Constructing a `String` from `Uint8Array` assuming UTF-8 semantics.
* Constructing a `String` from `Uint16Array` assuming WTF-16 semantics.
* Method on `String` that writes UTF-8 into a `Uint8Array` with the `encodeInto` semantics but returns an array of numbers instead of a WebIDL type.
* Method on `String` that writes WTF-16 into a `Uint16Array`.

-- 
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-873955639