"In addition to expanding the capabilities of raw linear memories, support was added for a new form of storage that is managed by the Wasm runtime automatically. WasmGC is low-level; a compiler targeting Wasm can declare the memory layout of its runtime data structures in terms of struct and array types, plus unboxed tagged integers, whose allocation and lifetime are then handled by Wasm."
"In the realm of memory, a single module now can declare multiple memories and directly access them, including copying data between them. This improvement allows tools like wasm-merge, which perform "static linking" on two or more Wasm modules by merging them into one, to work for all Wasm modules. It also paves the way for new uses of separate address spaces; examples provided were for security (separating private data), buffering, or instrumentation."
WebAssembly 3.0 advances memory and garbage collection with the WasmGC extension and a new form of runtime-managed storage alongside expanded raw linear memories. Compilers can declare runtime data layouts using struct and array types plus unboxed tagged integers whose allocation and lifetime are handled by Wasm. The WasmGC extension extends the Wasm type system and supports richer type references. A single module can now declare and directly access multiple memories and copy data between them. Multiple memories enable tools like wasm-merge to perform static linking and enable separate address spaces for security, buffering, or instrumentation. Browser support is widespread and standalone engine support is nearing completion.
Read at InfoWorld
Unable to calculate read time
Collection
[
|
...
]