Ben Smith
Ben Smith
See https://github.com/WebAssembly/spec/issues/1522. It seems that there wasn't an explicit test for this case, and wasm3's current behavior will be incorrect. e.g. ```wat (memory 1) (global i32 (i32.const 0) (data (global.get...
https://github.com/ncbray/wassembler/blob/master/system.js#L32 still uses the old Firefox nightly-style SharedTypedArrays. It would be nice to have the new way as well.
You should probably add an asm.js validation step. Sam pointed out that (for example) using Math.fround directly may not be allowed (I'm not sure).
``` char hexit(int x) { return "0123456789abcdef"[x]; } ``` This generates output: ``` (func $hexit (param i32) (result i8) (local i32 i32 i32 i32) (set_local 1 (get_local 0)) (set_local 2...
They should always walk up to the obstruction, even if they can't get past it
Similar to https://github.com/WebAssembly/tool-conventions/issues/133, it would be nice to be able to serve a wasm file without a name section, but have it associated with a wasm file that has a...
@sbc100 and I were just talking about how we might represent some of the relocation information in the WebAssembly text format. Nothing fully formed yet, but some ideas: * It...
@aardappel and I were discussing this briefly today: If you were to compile the following array access: ```c uint32_t array[100]; array[x] ``` in current wasm, you have to generate something...
See https://github.com/WebAssembly/meetings/blob/master/process/phases.md#4-standardize-the-feature-working-group. We discussed this in the March 21st CG meeting. There are now two implementations (in Chrome and Firefox) behind flags, as well as toolchain support in Emscripten. The...
Probably best to have these as options that can be enabled/disabled. Should be able to use Interaction Observer API for scrolling away: https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API