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
This is in rustler_sys, but it would be nice to have it wrapped more safely in rustler.
I'd be happy to contribute this one but could use some guidance on the API. I was thinking it would make sense to add ResourceBinary to rustler::resource (though maybe it should live in rustler::types::binary?). ResourceBinary::new would take a ResourceArc and a reference to a binary with a lifetime tied to the resource object. It would hold the cloned ResourceArc and the reference to the binary as well as the size of the binary.
Does that sound reasonable? Other than lifetime annotations, are there any other considerations for ensuring the binary data is handled properly if it's external to the resource object?
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
This is in
rustler_sys
, but it would be nice to have it wrapped more safely inrustler
.I'd be happy to contribute this one but could use some guidance on the API. I was thinking it would make sense to add
ResourceBinary
torustler::resource
(though maybe it should live inrustler::types::binary
?).ResourceBinary::new
would take aResourceArc
and a reference to a binary with a lifetime tied to the resource object. It would hold the clonedResourceArc
and the reference to the binary as well as the size of the binary.Does that sound reasonable? Other than lifetime annotations, are there any other considerations for ensuring the binary data is handled properly if it's external to the resource object?
The text was updated successfully, but these errors were encountered: