Re: HTTP and character encodings

On Tue, Sep 11, 2012 at 12:44 AM, Bryan O'Sullivan wrote:

On Mon, Sep 10, 2012 at 3:22 PM, Ganesh Sittampalam wrote:

...

I imagine this could be quite disruptive, but on the other hand people using the String instance are getting silently broken behaviour and a couple of people have been bitten by this recently.

I'm in favour of broken code breaking explicitly, rather than silently doing the wrong thing, so +1 to nuking the String instances in spite of the up-front pain.

+1. I've been bitten by the broken String instances, and now only use the ByteString instances. Erik