Because it is the most utilitarian way to get a bunch of strict ByteStrings out of a lazy one.
Yes it exposes an implementation detail, but the alternatives involve an unnatural amount of copying. -Edward Kmett On Sat, Apr 17, 2010 at 6:37 PM, Ashley Yakeley <ash...@semantic.org> wrote: > Ketil Malde wrote: > >> Do we also want to modify equality for lazy bytestrings, where equality >> is currently independent of chunk segmentation? (I.e. >> >> toChunks s1 == toChunks s2 ==> s1 == s2 >> but not vice versa.) >> > > Why is toChunks exposed? > > -- > Ashley Yakeley > > _______________________________________________ > Haskell-Cafe mailing list > Haskell-Cafe@haskell.org > http://www.haskell.org/mailman/listinfo/haskell-cafe >
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
