Re: ANNOUNCE: text 0.8.0.0, fast Unicode text support
kevinjardine at gmail.com
Wed Sep 1 02:31:12 EDT 2010
The issues involved with String, ByteString, Text and a few related
libraries were discussed at great length recently in this thread:
Basically, Chars are 32 bit integers and Strings are represented as a
list of Chars.
This is very convenient for small computations but often very
inefficient for anything large scale.
The String API is also missing various encoding related features.
Because of the limitations of String, various alternative libraries
have been proposed. Text is one important option.
You'll find much more detail on the above referenced thread.
On Sep 1, 8:13 am, Tako Schotanus <t... at codejive.org> wrote:
> On Wed, Sep 1, 2010 at 07:14, John Millikin <jmilli... at gmail.com> wrote:
> > > Don't forget, you can always improve the text library yourself. I love to
> > receive
> > > patches, requests for improvement, and bug reports.
> > Are there any areas in particular you'd like help with, for either
> > library? I'm happy to assist any effort which will help reduce use of
> > String.
> As a Haskell noob I'm curious about this statement, is there something
> intrinsically wrong with String?
> Or is it more a performance/resource problem when dealing with large amounts
> of text for example?
> (Like having to use StringBuilder in Java if you want to avoid the penalty
> of repeated String allocations when simply concatenating for example)
> Haskell-Cafe mailing list
> Haskell-C... at haskell.orghttp://www.haskell.org/mailman/listinfo/haskell-cafe
More information about the Haskell-Cafe