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

API for dropping Zaplib buffers #132

Open
janpaul123 opened this issue Mar 10, 2022 · 0 comments
Open

API for dropping Zaplib buffers #132

janpaul123 opened this issue Mar 10, 2022 · 0 comments
Labels
cruise enhancement New feature or request

Comments

@janpaul123
Copy link
Contributor

Something like zaplib.drop(buffer) to delete the buffer and make it unusable (just like when you pass a mutable buffer to Rust when passing ownership).

Currently you cannot control when immutable buffers are deallocated (it depends on garbage collection), so this gives you some control over it; thereby freeing memory that you don't use. With mutable buffers the workaround is to transfer it to Rust using callRustSync, and then immediately dropping it there.

@janpaul123 janpaul123 added enhancement New feature or request cruise labels Mar 10, 2022
@janpaul123 janpaul123 added this to the Basic stabilization milestone Mar 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cruise enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant