ByteString I/O Performance

[Udo Stenzel]

Peter Simons wrote:
> Is that so? How exactly does mutating a ByteString break the
> semantics of the pure function 'take'?

http://www.sgi.com/tech/stl/Rope.html 

That's roughly the same in a "practical" language.  Please read and
understand it completely before responding.


> A ByteString is a tuple
> consisting of a pointer into raw memory, an integer signifying
> the size of the front gap, and an integer signifying the length
> of the payload.

No, it's not.  You're confusing abstract data types and their
representation.  If you want to work with a tuple of a pointer and two
integers, by all means use a tuple of a pointer and two integers.


-Udo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://www.haskell.org/pipermail/libraries/attachments/20070906/b50da3cd/attachment.bin