-
|
Hi! I was wondering if there are any plans to take advantage of the in-place resizable array buffers which appear to now be supported in all browsers. If my understanding is correct, this potentially allows for resizing the wasm heap without invalidating views into it. I.e., it would allow for removing the limitation mentioned in the doc for TypedArray::view? My use case is that I'd like to expose a buffer for managing various data columns (coordinates, attributes) directly to JS so that I can avoid the overhead of calling into wasm for certain code flows. I think it also means that the checks in the generated code for https://www.proposals.es/proposals/Resizable%20and%20growable%20ArrayBuffers |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Interesting, unfortunately after some digging I found that this requires the new But generally speaking, there are no plans, but I would probably look into it as soon as it becomes viable. |
Beta Was this translation helpful? Give feedback.
-
|
Drats, didn't realize we're still missing the WASM memory part. Regardless, thanks for looking into this! |
Beta Was this translation helpful? Give feedback.
Interesting, unfortunately after some digging I found that this requires the new
WebAssembly.Memory.toResizableBuffer()API, which isn't available in any browser yet.But generally speaking, there are no plans, but I would probably look into it as soon as it becomes viable.