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
The Wasm/JS API is already merged into the Wasm spec (PR). The JS feature is already Stage 4 (merged into the standard)
Additional Signals
Emscripten would benefit from using this feature, as WebAssembly buffers has always been able to resize/grow. Since Wasm memories are exposed as ArrayBuffers, which by default cannot resize nor grow, growing the memories has to be expressed in unergonomic ways like detaching and requires manual polling.
The text was updated successfully, but these errors were encountered:
As a user of Emscripten, this is especially useful when using its support for multithreading and memory growth, since we have to constantly check if the buffer has been replaced before using it.
Thank you for proposing Resizable buffers integration in Wasm/JS API for inclusion in Interop 2025.
We are pleased to let you know that this proposal was accepted as part of the WebAssembly Additions focus area. You can follow the progress of this focus area on the Interop 2025 dashboard.
For an overview of our process, see proposal selection. Thank you for contributing to Interop 2025!
Description
This feature lets the Wasm/JS API vend resizable buffers in WebAssembly.Memory, making the Wasm API more ergonomic for JS integration.
Resizable buffers is an existing JS feature that added the ability to resize ArrayBuffer instances and to grow SharedArrayBuffer instances.
Specification
The Wasm/JS API is already merged into the Wasm spec (PR). The JS feature is already Stage 4 (merged into the standard)
Additional Signals
Emscripten would benefit from using this feature, as WebAssembly buffers has always been able to resize/grow. Since Wasm memories are exposed as ArrayBuffers, which by default cannot resize nor grow, growing the memories has to be expressed in unergonomic ways like detaching and requires manual polling.
The text was updated successfully, but these errors were encountered: