
29 Oct
2011
29 Oct
'11
8:18 a.m.
On 29 October 2011 12:05, Herbert Valerio Riedel
I propose to add optimized {to,from}Strict conversion functions between strict and lazy ByteStrings to the Data.ByteString.Lazy API.
+1 Maybe this is bikeshedding and I'm not sure I like it but we could also rename these functions to: toStrict -> fromLazy fromStrict -> toLazy Because we nowhere mention the word 'strict' in the bytestring API but we do mention to word 'lazy'. Any idea why "toStrict/simple #1" is faster than "toStrict/optimized #1"? Regards, Bas