Skip to content

Conversation

@alexcrichton
Copy link
Member

This commit is a follow-up to #1134 to require the gc feature flag be activated to use the (rec ...) construct from the GC wasm proposal. This additionally updates the text parsing and text printing to consider the structure of what's parsed for encoding/printing rather than the size of the types inside. Even a rec group of a single type prints a rec group or encodes it now instead of silently switching it back to a single-type encoding.

@alexcrichton
Copy link
Member Author

CI is failing due to #1178, nothing major though

This commit is a follow-up to bytecodealliance#1134 to require the `gc` feature flag be
activated to use the `(rec ...)` construct from the GC wasm proposal.
This additionally updates the text parsing and text printing to consider
the structure of what's parsed for encoding/printing rather than the
size of the types inside. Even a `rec` group of a single type prints a
`rec` group or encodes it now instead of silently switching it back to a
single-type encoding.
@alexcrichton alexcrichton force-pushed the gate-more-gc-features branch from 6c5c023 to 9f1c8f9 Compare August 25, 2023 16:47
@alexcrichton alexcrichton enabled auto-merge (squash) August 25, 2023 16:47
@alexcrichton alexcrichton merged commit 6d05053 into bytecodealliance:main Aug 25, 2023
@alexcrichton alexcrichton deleted the gate-more-gc-features branch March 19, 2024 21:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants