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,
Unfortunately I lack the time for a wholesale cleanup. If others have
proposals and are willing to supply the patches that's a different matter!
On 30/01/2013 08:01, Alfredo Di Napoli wrote:
Maybe (just my 2 cents!) since you are going to broke the API anyway, go
for it
and seize the occasion
Hi,
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.
The basic reason is that this instance is rather broken in itself. A
String ought to represent Unicode data, but the HTTP wire format is
On Tue, Jan 29, 2013 at 2:15 PM, Ganesh Sittampalam gan...@earth.li 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.
The basic reason is that this instance is rather broken in
On 29/01/2013 22:46, Johan Tibell wrote:
On Tue, Jan 29, 2013 at 2:15 PM, Ganesh Sittampalam gan...@earth.li 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
