Thomas Lively
Thomas Lively
@manoskouk proposed `array.copy` in https://github.com/WebAssembly/gc/pull/278#discussion_r810944560, but it was not included in that PR because it deserved separate discussion and a separate PR. Would anyone object to adding `array.copy` to the...
This repo has not had a lot of activity lately, so I'm wondering if this proposal is ready to move to phase 3. The phase 3 entry requirements are: 1....
This issue is meant to track which projects have updated their implementation to match the final proposal and have shipped by default, if applicable. | Project | status | |...
Currently the intrinsic header uses a different naming convention than the underlying SIMD instructions. The intrinsic name can be determined from the instruction name by prepending `wasm_`, turning the `.`...
Recently we have seen a couple proposals that introduce instructions with side effects that are not modeled in the WebAssembly semantics. Specifically, they are: 1. https://github.com/WebAssembly/design/issues/1344, which proposes tracing instructions...
Discussion at https://github.com/WebAssembly/gc/issues/208 is probably interesting to folks following this proposal. Let's keep the discussion on that original issue rather than forking the discussion, though.
The phase 4 requirements are: - Two or more Web VMs implement the feature. - Partially done. Chrome supports tail calls behind the #enable-experimental-webassembly-features flag. No other engines have implementations...
Previously when we parsed `string.const` payloads in the text format we were using the text strings directly instead of un-escaping them. Fix that parsing, and while we're editing the code,...
The GC spec has been updated to have heap type annotations on call_ref and return_call_ref. To avoid breaking users, we will have a graceful, multi-step upgrade to the annotated version...