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

Welcome @juj and others. https://whatwg.org/working-mode and https://whatwg.org/faq#adding-new-features might help provide some additional context, though I think we have enough to move forward here.

For SAB, is the copy that https://encoding.spec.whatwg.org/#dom-textdecoder-decode makes acceptable? If not, we'd somehow have to make decoding robust against input changing, right? It's not clear that's desirable. Either way, that would require a fair number of tests.

For scanning, we could add something to https://encoding.spec.whatwg.org/#textdecodeoptions API-wise. I'm not sure if encoding libraries expose such primitives though, but if not they could be added I suppose.

cc @hsivonen 

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