-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support MaybeUninit
and ManuallyDrop
#406
Comments
This makes sense. We already hande other standard types, so I don't think it should be too terrible to fix. |
Would that allow writing C functions as I'm trying to follow along the lines of what's there for NonNull and Cell, maybe I can come up with a PR. |
Yes it would. |
And yeah, doing what |
If I'm this comment, this is closed as of 0.15.0 (af6d2e3 in tree). @emilio / @Hywan can you confirm? (Thanks for adding this!) |
Yes, that's right! |
I think these should really be supported, as it is can be somewhat important when dealing with a C API. Since both are
#[repr(transparent)]
, and since (afaik) C fields do not have to be initialized as long as they aren't being used,MaybeUninit<T>
andManuallyDrop<T>
should probably be exopsed as whateverT
would translated to on its own.The text was updated successfully, but these errors were encountered: