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
If a user wants to pass these directly for use in FFI (not directly the intended use, but plausible and related to some uses), they need to be repr(transparent). Similarly, they could possibly use as_mut_ptr()/into_raw() that do not ever construct a Unique/&mut reference to the target (which would also be a less-pleasant workaround for the first thing).
The text was updated successfully, but these errors were encountered:
alloc::boxed::Box doesn't seem to be transparent due to future support around non-zero size handles to allocators, which might be something that might be wanted to be supported here too in the future. As you said, a middle ground providing as_mut_ptr()/into_raw() could be a good idea.
AliasableMut seems like a good fit for being made repr(transparent) however!
If a user wants to pass these directly for use in FFI (not directly the intended use, but plausible and related to some uses), they need to be repr(transparent). Similarly, they could possibly use as_mut_ptr()/into_raw() that do not ever construct a Unique/&mut reference to the target (which would also be a less-pleasant workaround for the first thing).
The text was updated successfully, but these errors were encountered: