You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
std::os::raw recommends to use core::ffi instead, but for std crates using core directly seem to trigger some warnings. The std::ffi::* offers the same types like c_char and c_int as core::ffi::*, plus it offers the newer types like CStr in there. Would it make sense to consistently use just the std::ffi::* for all C types in the generated code?
P.S. I am aware that this can be done with .ctypes_prefix("::std::ffi") param - but the question is if this should be done by default?
The text was updated successfully, but these errors were encountered:
std::os::raw
recommends to usecore::ffi
instead, but for std crates using core directly seem to trigger some warnings. Thestd::ffi::*
offers the same types likec_char
andc_int
ascore::ffi::*
, plus it offers the newer types likeCStr
in there. Would it make sense to consistently use just thestd::ffi::*
for all C types in the generated code?P.S. I am aware that this can be done with
.ctypes_prefix("::std::ffi")
param - but the question is if this should be done by default?The text was updated successfully, but these errors were encountered: