> I've seen std::ptr::null more than I ever have Foreign.Ptr.nullPtr. Probably because we need to work with the C API a great deal right now, but that should c

> I've seen std::ptr::null more than I ever have Foreign.Ptr.nullPtr. Probably because we need to work with the C API a great deal right now, but that should change as more and more things are written in Rust. Still, the unsafe boundary helps by removing the ability to dereference a raw pointer in safe code - something that Haskell doesn't have.