Re: [whatwg/encoding] Consider decode() with offset/length (#219)

Yeah, see https://github.com/whatwg/encoding/issues/69#issuecomment-434539796 onward. https://github.com/whatwg/encoding/issues/69#issuecomment-434718429 mentions how you could optimize the view allocations away in Wasm (with theoretical host bindings).

1. Is the performance drawback consistent across browsers? How bad is it? (The bug doesn't go into much detail and it seems like a lot of effort to get access to the linked document.)
2. Has TC39 considered some kind of mutable view to help with these scenarios? It seems bad if we would have to do this for each API taking a view.
3. If we want speed is overloading the way to go? Dictionaries? (Why not use Wasm with theoretical host bindings?)

-- 
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/219#issuecomment-643570583