Ben Visness

It would be very useful to see what the spec ramifications would be. My prototype in Firefox is a bit of a hack, but does work well enough in common...

You'll have to explain to me a scenario where this is breaking, I guess. Shipping this would not break existing apps, because existing apps would only pass ArrayBuffer to a...

That would certainly be my preference, since it seems somewhat impractical to actually opt in in many places. For example, `Request.body`. That's a getter that returns a ReadableStream. Is that...

Would it make sense to create a PR for this SAB update? I'd appreciate being able to follow the actual spec modifications so that I can ensure my Firefox prototype...

This whole space is further muddied by the [type reflection proposal](https://github.com/WebAssembly/js-types/blob/main/proposals/js-types/Overview.md), which is still languishing in phase 3. I think we are probably long overdue to revisit it. FWIW, [this](https://searchfox.org/firefox-main/rev/c7b4ff2aadfce11e419c226b7839b0348258a504/js/src/wasm/WasmValType.cpp#160)...

It might be possible to add "guards" to the wast, e.g. `(if-supports "multi-memory" (module ...))`. In SpiderMonkey we generate JS from the wast, and then patch many of the JS...

For an MxN situation, I figure you have to either do one file per M or one file per N, so either way a test author will be frequently jumping...

I'll revert the gemfile stuff, yeah.

Done.

I imagine that it would be equality as defined for Number, which is [defined](https://tc39.es/ecma262/multipage/notational-conventions.html#sec-mathematical-operations) as typical floating point equality, meaning -0 would equal +0.