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
{{ message }}
This repository has been archived by the owner on Jun 23, 2023. It is now read-only.
Sometimes we may wish to use ffi.Callback to represent a function pointer that's being passed to a native function as a parameter. Today, these types get mapped as ffi.Function which isn't compatible. We should consider how to support a typed solution that allows either:
Select ffi.Function or ffi.Callback via clangffi flags or other user config (ideally selection occurs at a function level)
Provide a typing that allows for either, and let the caller decide
The text was updated successfully, but these errors were encountered:
Sometimes we may wish to use
ffi.Callback
to represent a function pointer that's being passed to a native function as a parameter. Today, these types get mapped asffi.Function
which isn't compatible. We should consider how to support a typed solution that allows either:ffi.Function
orffi.Callback
viaclangffi
flags or other user config (ideally selection occurs at a function level)The text was updated successfully, but these errors were encountered: