Re: [encoding] Serializing internal TextDecoder state? (#7)

> One way to deal with this would be to rewrite all our decoders to be stateless (turn them from classes to mere functions basically) and to introduce a separate common state management wrapper for all the callers that don't need to deal with the state themselves.

I thought about this more. The storage idea I had it mind when I wrote the above would make the things inefficient on the subsequent call. So I withdraw the notion that if we did a rewrite, state wouldn't need to be private and different on a per decoder type basis.

I'm still really curious about a super-important use case. At this point I'd close this as WONTFIX due to too much hassle for too little benefit.

(Aside: Is there an example of another platform, even a single-implementation one, that supports serializing and deserializing in-flight decoders?)

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/7#issuecomment-153665834