ByteString I/O Performance
u.stenzel at web.de
Thu Sep 6 16:00:26 EDT 2007
Peter Simons wrote:
> Is that so? How exactly does mutating a ByteString break the
> semantics of the pure function 'take'?
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://www.haskell.org/pipermail/libraries/attachments/20070906/b50da3cd/attachment.bin
More information about the Libraries