Does this imply that in wasm32, we can create ArrayBuffer objects, whose storage does not count towards the 4GB limit ?
What is the absolute fastest way to read/write wasm32 <-> ArrayBuffer ?
T: Copy, can we create a
MyVec<T>that is backed by an ArrayBuffer ?
If you try to pass them to wasm as an array you'll have to copy them, and that will count torwards the 4GB limit (otherwise how would you be able to address them?).
Alternatively you can keep it in js land and access it only through host functions, but do note that calling into the host is relatively slow.
Question 3. and 4. depend on how you choose to represent the ArrayBuffer in wasm land.
I wonder what block size we need to copy over from ArrayBuffer to wasm32 land to have it dwarf out the js call overhead. 4kb? 64kb 1MB ?