This repository has been archived by the owner on May 11, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 147
How to allocate memory #48
Comments
Shameless plug: perhaps something like this can be of some use? |
I must admit this is an area I haven't yet dedicated too many cycles to. @cznic all your packages are on my radar :) |
Thanks, for now I realized the easiesz way is to provide these as runtime methods in my module as alloc and dealloc (using rust for the wasm code this is pretty straightforward) and the exposed vm.Memory() is enough to do what I need for now. I‘ll provide an example here once I have things working.
…On 16. Dec 2017, 12:54 +0100, Sebastien Binet ***@***.***>, wrote:
I must admit this is an area I haven't yet dedicated too many cycles to.
Obviously, that's something we want to provide.
@cznic all your packages are on my radar :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@dignifiedquire there's some work happening in the memory allocation/manipulation area: #59 do you have some input? (here or directly on the PR.) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am trying to implement a way of passing more complex data between wasm and go and was looking for something like
malloc
which emscripten provides to allocate a new memory block, where I can write data into from the outside, to make it available to the program. EgThe text was updated successfully, but these errors were encountered: