Re: [encoding] Fix #18: remove UTF-16 support from TextEncoder (#36)

Diff looks good.

We don't have stats on whether the TextEncoder constructor is typically called with or without the optional argument. But knowing that developers do like to fill in the blanks, it would surprise me if there weren't uses of `new TextEncoder("utf-8")` out there. Which means we'll never be able to use the first argument for anything else. I'm tempted to leave the optional argument it in there, with the "throw if not a utf-8 label" behavior.

---
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/pull/36#issuecomment-196922072