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
Sharing linear memory between WASM and JavaScript without shared memory management is slightly hazardous -- one side can easily clobber what the other wrote. It would be beneficial to provide C memory management functionality in wasm libc, that can be used for both JS and WebAssembly, similar to what Rust does.
The text was updated successfully, but these errors were encountered:
I think tools that ease the interop between JS and wasm are outside the scope of reference-sysroot.
One thing that should significantly help in this area is the host bindings proposal. That will allow one to pass a slice of linear memory to a function, rather than just exporting all of memory.
Host bindings has evolved into WebIDL bindings which is evolving further and aiming to be not specific to the Web. It's an ongoing story, but that's where I expect this issue will be solved, rather than in reference-sysroot.
Sharing linear memory between WASM and JavaScript without shared memory management is slightly hazardous -- one side can easily clobber what the other wrote. It would be beneficial to provide C memory management functionality in wasm libc, that can be used for both JS and WebAssembly, similar to what Rust does.
The text was updated successfully, but these errors were encountered: