Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document copy vs borrow semantics of FFI functions #83

Open
cstepanian opened this issue Apr 28, 2021 · 0 comments
Open

Document copy vs borrow semantics of FFI functions #83

cstepanian opened this issue Apr 28, 2021 · 0 comments
Labels
2-points Sprint points (2 = very easy)

Comments

@cstepanian
Copy link

Some iterators return copies to Rust data that need to be deleted with specific functions.
Others merely return pointers (borrows) to data, that the caller need not manually clean up,
other than making sure that the pointer does not dangle after the underlying storage is freed.

Note that all Iterators need to be deleted after use -- it is only the items that may or may not
be copied.

Iterators which only borrow for each item:

  • ProviderStateIterator
  • MessagePactMessageIterator

Iterators which allocate for each item:

  • MessageMetadataIterator (message_metadata_pair_delete)
  • ProviderStateParamIterator (provider_state_param_pair_delete)
  • MessagePactMetadataIterator (message_pact_metadata_triple_delete)
@cstepanian cstepanian added the 2-points Sprint points (2 = very easy) label Apr 28, 2021
@cstepanian cstepanian self-assigned this Apr 28, 2021
@cstepanian cstepanian removed their assignment Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2-points Sprint points (2 = very easy)
Projects
None yet
Development

No branches or pull requests

1 participant