20 Jun
2012
20 Jun
'12
12:40 p.m.
On 20 June 2012 11:40, Lauri Alanko
There's a minor lapse in Data.ByteString.Unsafe: unsafePackMallocCString, unlike the other unsafePack* -functions, doesn't have a variant with an explicit length. This is useful when interfacing with C libraries that return a blob of binary data that the caller must free. Attached is a darcs patch that adds it.
+1