
Maybe (just my 2 cents!) since you are going to broke the API anyway, go
for it
and seize the occasion to really clean up :)
Obviously I'm saying this from a non-http-user point of view, maybe if I had
some code in production affected by this, my suggestion would have been
different :P
Regards,
A.
On 30 January 2013 07:00, Ganesh Sittampalam
On 29/01/2013 22:46, Johan Tibell wrote:
On Tue, Jan 29, 2013 at 2:15 PM, Ganesh Sittampalam
wrote: tl;dr: I'm planning on removing the String instances from the HTTP package. This is likely to break code. Obviously it will involve a major version bump.
I think it's the right thing to do. Providing a little upgrade guide should help things to go smoother.
One obvious cheap-and-dirty migration is via a newtype wrapper for String that embeds the old broken behaviour (char8 encoding). Perhaps the package should provide that? (with appropriate warnings etc)
Ganesh
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe