On Sunday, 28 September 2014 at 23:48:54 UTC, Walter Bright wrote:
I think it was you that suggested that instead of throwing on invalid UTF, that the replacement character be used instead? Or maybe not, I'm not quite sure.

Regardless, the replacement character method is widely used and accepted practice. There's no reason to throw.

This I'm OK to stand stand behind as acceptable change (should we decide to go with). It will kill the "auto-decode throws and uses the GC" argument.

Reply via email to