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

Was talking to @bsittler about using TextDecoder and he mentioned that he needs to be able to serialize the current decoding state to IndexedDB in order to survive e.g. service worker upgrades. TextDecoder definitely has internal state (a few bytes left in its internal "stream" variable, basically) which can get lost in this manner. It would be great to expose this, and allow construction of a new TextDecoder primed with that state.

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