1860816 - Ship multi-memory

Status: RESOLVED FIXED

(Core :: JavaScript: WebAssembly, task, P2)

Description

[Ryan Hunt [:rhunt]]

Multi-memory has reached phase 4 and is pretty stable. We should be able to ship it soon.

Comment 1

[Ben Visness [:bvisness]]

Attachment: Bug 1860816: Ship wasm multi-memory. r=rhunt

:)

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/663bb21e6b10
Ship wasm multi-memory. r=rhunt

Comment 3

[Serban Stanca [:SerbanS]]

https://hg.mozilla.org/mozilla-central/rev/663bb21e6b10

Comment 4

[Ryan VanderMeulen [:RyanVM]]

Please add a relnote nomination for this assuming this is something we should call out in the Fx125 relnotes.

Comment 5

[Ben Visness [:bvisness]]

Release Note Request (optional, but appreciated)
[Why is this notable]: We are enabling a major WebAssembly proposal by default.
[Affects Firefox for Android]: Yes
[Suggested wording]: Enabled WebAssembly multi-memory by default. Wasm multi-memory allows wasm modules to use and import multiple independent linear memories. This enables more efficient interop between modules, and better polyfills for upcoming wasm standards like the component model.
[Links (documentation, blog post, etc)]: https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md

Comment 6

[Ryan VanderMeulen [:RyanVM]]

Added to the Fx125 relnotes.

Comment 7

[Hamish Willee]

FYI MDN Docs for this can be tracked in https://github.com/mdn/content/issues/32777. They are mostly complete, and in review.