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
- Uniformise how indirections (references, Boxes, raw pointers) are
handled. (more specific indirection types with specific guarantees are
not handled yet)
- Indirections that are compiled to a "thick pointer" (indirections to
slices, dyn objects, *not* foreign !Sized types) have better messaging
around them.
- Now, the pointee of a FFI-safe indirection is always considered safe.
This might be a regression, if we consider that an extern function's
API should describe how the function can be used by the non-defining
side of the FFI boundary.
However, enforcing this everywhere would force the user to perform
an unreasonable amount of typecasts to/from opaque pointers.
There is something better to do here, but it will be left to another
PR.
0 commit comments