Proposal: add ByteString support to unix:System.Posix.IO API

Gábor Lehel illissius at
Thu Mar 3 18:42:55 CET 2011

On Thu, Mar 3, 2011 at 5:55 PM, Brandon S Allbery KF8NH
<allbery.b at> wrote:
> Hash: SHA1
> On 3/2/11 21:38 , wren ng thornton wrote:
>> But that does raise the issue: if we are to (eventually) remove the string
>> versions and put the bytestring versions in situ, then how should the
>> migration proceed? I'd suggest putting the functions in
>> System.Posix.IO.ByteString for the interim; this has the benefit that I
>> could release a compatibility library allowing people to upgrade without
>> changing their GHC, if need be.
> It occurs to me that, if we're going to remove String versions, it should
> happen everywhere and in a coordinated way.

What is the benefit from removing String versions (as opposed to just
adding ByteString (and/or Text) ones alongside them)?

> - --
> brandon s. allbery     [linux,solaris,freebsd,perl]    allbery.b at
> system administrator  [openafs,heimdal,too many hats]                kf8nh
> Version: GnuPG v1.4.11 (Darwin)
> Comment: Using GnuPG with Mozilla -
> dVkAn0CI5LrxgjVc6ZugdXebPzZu87J9
> =dtDw
> _______________________________________________
> Libraries mailing list
> Libraries at

Work is punishment for failing to procrastinate effectively.

More information about the Libraries mailing list