No. I don't think that works. As someone who has written a LOT of ffi, you need these kinds of types and I'm not sure how to make these more FFI safe in the first place
-
This Tweet is unavailable.
-
This Tweet is unavailable.
-
It doesn't have a different memory repr, but it does have narrowed provenance for the pointer you get. That's why the as_ptr method for slices first makes *const [T] and then makes *const T, in that very specific ordering. Sounds stupid, but RalfJ assures me it's true.
Wow that basically eliminates the ability to have a safer version of `as_ptr` for many types then. That's really unfortunate.
-
-
Does it? Why can't it be a transparent type that is basically just the pointer, but has a PhantomData reference to the original CStr?
-
Because a transparent type that is basically just the pointer can't be passed to a function that takes a pointer
- 8 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.