-
Simon Marlow authored
Which isn't allowed using the ordinary newForeignPtr any more, it has to be done with Foreign.Concurrent.newForeignPtr.
51f05d57
Which isn't allowed using the ordinary newForeignPtr any more, it has to be done with Foreign.Concurrent.newForeignPtr.