Remove the TextDecoder and TextEncoder APIs

[SimonSapin]

Hi,

If #3 is resolved and the spec’s error handling behavior can be obtained with the "normal" API, I believe that the TextDecoder and TextEncoder APIs should be removed. The reasons are:

• It doesn’t seem to do anything useful that the rest of the API doesn’t already do.
• The spec says "Non-browser implementations are not required to implement this API."
• It is designed for JavaScript (options dicts, TypeError, …) and doesn’t translate well into Rust.
• I don’t personally find it very good anyway.

Instead, the get_encoding() function should be public. It is useful anyway when dealing with multiple encoding hints. (See for example the relevant CSS spec)

[lifthrasiir]

For now please see my comment in #3. By the way, thank you for pointing that spec, I agree on your thought on the encoding enumeration API.

[lifthrasiir]

They are gone as of 3025543.