[web-devel] http-types: Request for comments for major release
michael at snoyman.com
Sun Jul 1 05:59:23 CEST 2012
On Sun, Jul 1, 2012 at 5:23 AM, Aristid Breitkreuz <aristidb at gmail.com> wrote:
> I'd like to deprecate the Ascii type, and use ByteString directly, to
> simplify the module structure. Any objections?
Well, Ascii is just a type synonym, so all you'd really be doing is
changing around the type signatures. From a compatibility standpoint,
a library could easily be compliant with both the old and new versions
(either by switching to using ByteString everywhere, or if you still
export the Ascii type synonym, using there). In other words, no
> 2012/6/30 Michael Snoyman <michael at snoyman.com>
>> What's the timeframe on the http-types release? It might be that it
>> fits in perfectly with the upcoming wai release (probably in the next
>> two weeks or so). Either way, it's not a problem to bump max versions
>> mid-cycle. If the code can work unmodified with either version, that's
>> a really easy change. But even breaking changes can be accomodated
>> (with a bit of pain) using conditional compiling; that's what we ended
>> up doing for blaze-html 0.5.
> It depends on whether anybody has a feature request. If not, it might be
> done in less than 2 weeks.
>> I think that splitting up into a few submodules and keeping a master
>> module re-exporting everything is a good move. And of course, removing
>> deprecated functions is a good thing too. Otherwise, I don't have much
>> of an opinion here, http-types has been one of those "it works and I
>> don't have to think much about it" packages :).
> Already changed in the Github. Also glad to hear that http-types "just
> works" for you. :)
More information about the web-devel