ByteString I/O Performance

Seth Kurtzberg seth at
Sun Sep 2 23:55:34 EDT 2007

-----Original Message-----
From: libraries-bounces at [mailto:libraries-bounces at] On Behalf Of Bryan O'Sullivan
Sent: Sunday, September 02, 2007 11:23 PM
To: Peter Simons
Cc: libraries at
Subject: Re: ByteString I/O Performance

Peter Simons wrote:

> One way to get malloc() out of the picture would be to provide a
> variant of hGet that takes an existing, pre-allocated buffer as an
> argument, so that the user can allocate a ByteString once and re-use
> it for every single hGet and hPut.

This is already quite easy to do.  See unsafeUseAsCStringLen in 
Data.ByteString.Base, and hGetBuf in System.IO.

Is it possible without resorting to an unsafeXXX function?

Libraries mailing list
Libraries at

More information about the Libraries mailing list