The memory64 proposal adds support for linear WebAssembly memories with size larger than 2^32 bits. It provides no new instructions, but instead extends the existing instructions to allow 64-bit indexes for memories and tables.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
Memory64 is fully debuggable in DevTools.
The proposal comes with exhaustive spec tests; we pass them.
The feature would not change any existing behavior unless the website specifically uses the new instructions to create and access large memories. As so far no website has adopted this feature in production use, a Finch trial would provide no coverage at all.
Shipping on desktop | 133 |
DevTrial on desktop | 112 |
Shipping on Android | 133 |
DevTrial on Android | 112 |
Shipping on WebView | 133 |
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAPAU7RzZgYMSoD8-Gb_edSP29fLEg4oJjg0WZaTwS6F1%2BrPs%2Bw%40mail.gmail.com.
LGTM2
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cbdb1124-0db7-4713-aefe-a6d6e431a9f7%40chromium.org.