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
Is your feature request related to a problem? Please describe.
I am creating an FFI library where I want to pass in a number of thing_trait_objects. I then store these into an object and this object is used within a web service (ie Warp inside Tokio). For this to work the object I pass in needs to be Sync + Send. Sync + Send depend upon the enclosed objects. In particular the vTable is giving me the error NonNull<HealthProbeFuncsVtable> cannot be sent between threads safely`
How can I enable the vTable to be Safe + Sync
Describe the solution you'd like
An example of how to add Sync + Send to the vTable. And some discussion on risks or why/why not.
Describe alternatives you've considered
I don't really see an alternative on having Sync + Send available. I was wondering if I can explicitly add this and unsure if that is sensible/safe.
Additional context
Not that I can think at moment.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I am creating an FFI library where I want to pass in a number of thing_trait_objects. I then store these into an object and this object is used within a web service (ie Warp inside Tokio). For this to work the object I pass in needs to be Sync + Send. Sync + Send depend upon the enclosed objects. In particular the vTable is giving me the error
NonNull<HealthProbeFuncsVtable>
cannot be sent between threads safely`How can I enable the vTable to be Safe + Sync
Describe the solution you'd like
An example of how to add Sync + Send to the vTable. And some discussion on risks or why/why not.
Describe alternatives you've considered
I don't really see an alternative on having Sync + Send available. I was wondering if I can explicitly add this and unsure if that is sensible/safe.
Additional context
Not that I can think at moment.
The text was updated successfully, but these errors were encountered: