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

Investigate memory allocation/deallocation alternatives for wasmer #110

Open
ThetaSinner opened this issue May 17, 2024 · 0 comments
Open

Comments

@ThetaSinner
Copy link
Member

See #109 (comment)

Trying to use vectors for allocation and deallocation is risky because it depends on the internals of vector and how it chooses to do allocation. Is there an allocator we could use which hides some of these details? Or possibly just use layout/alloc/dealloc from the stdlib to more directly manage memory. Arrays allocated with alloc can still be wrapped in a slice or vector to be read.

@ThetaSinner ThetaSinner converted this from a draft issue May 17, 2024
@cdunster cdunster self-assigned this Oct 22, 2024
@jost-s jost-s moved this from Backlog to Ready for refinement in Holochain Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Ready for refinement
Development

No branches or pull requests

2 participants