Hi,
On 02/05/2014 09:55, Malthe Borch wrote:
It blows up – as expected, because "ascii" is a limited encoding.
It's not just ascii. That said, blowing up at encoding time is terrible because
you don't know where the error comes from. This is especially a huge problem on
Python 3 right now because of how frequently you piggyback broken unicode
through surrogate escapes.
By the time you encode and it tells you the string is invalid, it's impossible
to figure out where it came from.
Regards,
Armin
_______________________________________________
Rust-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/rust-dev
