fitzgen opened PR #13406 from fitzgen:update-wasm-gc-stability-in-docs to bytecodealliance:main:
I think we can consider it fuzzed between the new GC accessors fuzzer, wasm-smith's Wasm GC support, and the ongoing GC ops fuzzer work. Additionally, when we accidentally introduced GC-related bugs recently (e.g. when splitting GC heap tunables out from the existing memory tunables) the fuzzers quickly and successfully found these bugs.
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
fitzgen requested alexcrichton for a review on PR #13406.
fitzgen requested wasmtime-default-reviewers for a review on PR #13406.
github-actions[bot] added the label wasmtime:docs on PR #13406.
:thumbs_up: alexcrichton submitted PR review.
alexcrichton added PR #13406 Update Wasm GC stability docs to the merge queue.
:check: alexcrichton merged PR #13406.
alexcrichton removed PR #13406 Update Wasm GC stability docs from the merge queue.
Last updated: Jun 01 2026 at 09:49 UTC