As of yesterday, GHC's implementation of MarshalAlloc.allocaBytes is now based on ByteArrays, and is much faster. Since this effectively removes the reason for having UnsafeCString, and since there was some objection to it in the first place, I propose to remove it. Any objections? Cheers, Simon
"Simon Marlow" <simonmar@microsoft.com> wrote,
As of yesterday, GHC's implementation of MarshalAlloc.allocaBytes is now based on ByteArrays, and is much faster. Since this effectively removes the reason for having UnsafeCString, and since there was some objection to it in the first place, I propose to remove it. Any objections?
Sounds good to me. BTW, after another teaching-enforced break, there'll be an update of the FFI definition soon. I am currently integrating all the FFI libraries. Cheers, Manuel
participants (2)
-
Manuel M. T. Chakravarty -
Simon Marlow