well, no, you can control the rust bindings but maybe not the C header.
-
Yeah that seems really easy to try doing a pointer cast instead of a dereference. Making &c_char created from a *c_char not UB seems most tractable to me
The biggest upside of that RFC is that if CStr guarantees its memory repr we can have bindgen always generate &CStr for arguments, but: This means we lose the ability to do takes_cstr(returns_cstr()) That doesn't help with all the existing code out there taking *const char
-
-
Also not everyone uses bindgen and I don't necessarily expect everyone writing a c binding to know "&CStr has the same memory repr as *const c_char and I should always use that"
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.