Re: [whatwg/encoding] New TextDecoder.decode() API needed for Wasm multithreading (#172)

An option to stop deciding on null was discussed very early on in the API design. I think we rejected it due to lack of use cases at the time. 

We'd need to make sure the decoding algorithms play nicely with it, and there is no ambiguity about a null in the middle of a multibyte sequence. (I'd assume this is designed into the encodings, but don't actually know.)

-- 
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/172#issuecomment-461210339