FPS/Data.ByteString candidate

Donald Bruce Stewart dons at cse.unsw.edu.au
Mon Apr 24 21:10:13 EDT 2006


john:
> On Sun, Apr 23, 2006 at 05:27:43PM +1000, Donald Bruce Stewart wrote:
> > Following discussion, I've tagged FPS 0.4, a candidate for the base
> > library. Changes:
> > 
> >     * Renamed to Data.ByteString(ByteString)
> >     * Improved documentation
> >     * Tweaks to build under ghc 6.6
> >     * Added: getLine, getContents, putStr, putStrLn, zip, unzip, zipWith
> >     * Much faster: elemIndices, lineIndices, split, replicate
> >     * More automagic benchmarks and QuickCheck tests.
> 
> Can we get rid of every reference to 'Char' in the interface? a search
> and replace setting them to 'Word8' should do it. Casting between Word8
> and Char is just very wrong. a Char based FastString can be built on top
> of it, but we want to be typesafe in any interface.

Ok. I appreciate this concern.

I'll follow Simon Marlow's library here and partition it into, something
like:

    Data.ByteString             -- the core ByteString and Word8 operations
    Data.PackedString.Latin1    -- Char level packed string functions

John (and Ashley?) would this be ok?

-- Don


More information about the Libraries mailing list