Ryan Hunt

In the shell it should get enabled with `-P wasm_memory64` (-P enables prefs). In the browser, about:config it should be `javascript.options.wasm_memory64`. I believe nightly builds have it enabled by default.

I approve this license change.

> Interesting! > > Do you have ideas for how the wasm would be generated for this API? I'm curious what use cases you have in mind. (Specifically, it seems...

> It is not clear to me whether slices correspond to whole ArrayBuffers or just a portion of them. A coercion down to the underlying array buffer would correspond to...

> > > We should probably support loading and storing [half-precision floating point numbers](https://github.com/WebAssembly/half-precision/blob/main/proposals/half-precision/Overview.md) as well > > > > > > I believe we would just need a `slice.load_v128`...

> As a C programmer, it feels unfortunate to me that Wasm continues to distance itself from being a good target for C. Sure, this feature doesn’t specifically introduce the...

For Ion in SpiderMonkey, we'll generate equivalent IR for `v128.constant 0` and using `local.get` when the local is zero-initialized once (by default or explicitly). Baseline will use a memory load...

A couple thoughts here, thanks for writing this up! > Semantic equivalence I think that _true_ semantic equivalence here will be very difficult. It's already the case that engines could...

This would be fine with me.

I would be concerned that if lazy validation is started to be widely used in engines, we may eventually find all engines are required to implement it to remain web-compatible....