Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update pop text syntax #6251

Merged
merged 1 commit into from
Jan 30, 2024
Merged

Update pop text syntax #6251

merged 1 commit into from
Jan 30, 2024

Conversation

tlively
Copy link
Member

@tlively tlively commented Jan 26, 2024

Rather than (pop valtype*), use (pop valtype), where valtype is now
allowed to be a tuple. This will make it possible to parse un-folded multivalue
pops in the new text parser. The alternative would have been to put an arity in
the syntax like we have for other tuple instructions, but that's much uglier.

@tlively tlively requested a review from kripken January 26, 2024 18:39
@tlively
Copy link
Member Author

tlively commented Jan 26, 2024

@tlively tlively force-pushed the pop-syntax branch 2 times, most recently from 4ada05f to 07d53b6 Compare January 29, 2024 20:51
@tlively
Copy link
Member Author

tlively commented Jan 29, 2024

Merge activity

  • Jan 29, 6:36 PM: @tlively started a stack merge that includes this pull request via Graphite.
  • Jan 29, 7:04 PM: Graphite rebased this pull request as part of a merge.
  • Jan 29, 7:31 PM: @tlively merged this pull request with Graphite.

Base automatically changed from parser-tuple-sets to main January 30, 2024 00:03
Rather than `(pop valtype*)`, use `(pop valtype)`, where `valtype` is now
allowed to be a tuple. This will make it possible to parse un-folded multivalue
pops in the new text parser. The alternative would have been to put an arity in
the syntax like we have for other tuple instructions, but that's much uglier.
@tlively tlively merged commit 88d6b7c into main Jan 30, 2024
15 checks passed
@tlively tlively deleted the pop-syntax branch January 30, 2024 00:31
radekdoulik pushed a commit to dotnet/binaryen that referenced this pull request Jul 12, 2024
Rather than `(pop valtype*)`, use `(pop valtype)`, where `valtype` is now
allowed to be a tuple. This will make it possible to parse un-folded multivalue
pops in the new text parser. The alternative would have been to put an arity in
the syntax like we have for other tuple instructions, but that's much uglier.
@gkdn gkdn mentioned this pull request Aug 31, 2024
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