Closed Bug 1860816 Opened 8 months ago Closed 4 months ago

Ship multi-memory

Categories

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

task

Tracking

()

RESOLVED FIXED
125 Branch
Tracking Status
relnote-firefox --- 125+
firefox125 --- fixed

People

(Reporter: rhunt, Assigned: bvisness)

References

Details

(Keywords: dev-doc-complete)

Attachments

(1 file)

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

Depends on: 1842293
Assignee: nobody → bvisness
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 125 Branch

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

Flags: needinfo?(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

relnote-firefox: --- → ?
Flags: needinfo?(bvisness)

Added to the Fx125 relnotes.

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

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: