For JavaScript features we have the following way to enable experimental/staged features:

V8:
--harmony-staged
--es-staging
Chrome:
chrome://flags/#enable-javascript-harmony

This enables web developers, partners and standard bodies to experience soon-to-be-shipped JavaScript features before we can actually ship them.

We should create a similar machinery for WebAssembly language features. WebAssembly features that implement a spec proposal are allowed to be staged behind. Pure backend changes that do not alter the Web Platform's API surface still should use --future instead. Let's introduce the following flags:

V8:
--webassembly-language-staged
Chrome:
chrome://flags/#webassembly-language-staged (Enabled/Disabled[Default])


 

For JavaScript features we have the following way to enable experimental/staged features:

V8:
--harmony
--es-staging
Chrome:
chrome://flags/#enable-javascript-harmony

This enables web developers, partners and standard bodies to experience soon-to-be-shipped JavaScript features before we can actually ship them.

We should create a similar machinery for WebAssembly language features. WebAssembly features that implement a spec proposal are allowed to be staged behind. Pure backend changes that do not alter the Web Platform's API surface still should use --future instead. Let's introduce the following flags:

V8:
--webassembly-language-staging
Chrome:
chrome://flags/#webassembly-language-staging (Enabled/Disabled[Default])