Proposal: Add {to, from}Strict conversion functions between strict and lazy ByteStrings

[Brandon Allbery]

On Sun, Oct 30, 2011 at 09:47, Don Stewart <dons00 at gmail.com> wrote:

> Just as a historical note, they were intentionally left out of the
> original bytestring library, as it was felt it would only encourage mixing
> up lazy and strict bytestrings, with resulting poor and confusing
> performance.


I think the fact that the issue has come up demonstrates that this was the
wrong solution.  In particular, this design has led to a bit too much
"every library chooses one and you lose or are forced to convert to a
possibly inappropriate representation if you don't agree".

-- 
brandon s allbery                                      allbery.b at gmail.com
wandering unix systems administrator (available)     (412) 475-9364 vm/sms
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20111030/9606131c/attachment.htm>