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
Currently, a lot of bindings for optional in or out pointer parameters of bindings are using Option around the possibly null pointer, which:
Makes a param size larger then a size of a ptr,
Requires casting to raw pointer to be a real None check and not a no-op.
Making binding rely on Option<NonNull<T>> should be a general and quite easy improvement (though, it will not allow to express if the param can be mutated by bound function). Other then this little drawback, are there any other reasons not to opt for this kind of binding generating?