Repository navigation
Decode and encode GC instructions, and refuse them in the translator - #498
Merged
Merged
Conversation
#489 implemented head types, but WasmParser and WAT rejected every GC instruction as unknown. WasmParser now decodes them when the `gc` feature is enabled, and WAT parses and encodes their text forms. The translator refuses each one with `<name> is not supported yet`.
MaxDesiatov
marked this pull request as ready for review
October 5, 2026 13:50
kateinoigakukun
approved these changes
Oct 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#489 implemented heap types, but WasmParser and WAT rejected every GC instruction as unknown. WasmParser now decodes them when the
gcfeature is enabled, and WAT parses and encodes their text forms. The translator refuses each one with<name> is not supported yet.