Skip to content

Conversation

tlively
Copy link
Member

@tlively tlively commented Jan 26, 2024

These instructions always pop a single value, except when tuples are involved,
in which case they need special handling to know how many values to pop.

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

tlively commented Jan 26, 2024

@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, 6:37 PM: Graphite rebased this pull request as part of a merge.
  • Jan 29, 7:03 PM: @tlively merged this pull request with Graphite.
Base automatically changed from parser-tuple-types to main January 29, 2024 23:36
These instructions always pop a single value, except when tuples are involved, in which case they need special handling to know how many values to pop.
@tlively tlively merged commit c0046ad into main Jan 30, 2024
@tlively tlively deleted the parser-tuple-sets branch January 30, 2024 00:03
radekdoulik pushed a commit to dotnet/binaryen that referenced this pull request Jul 12, 2024
…bAssembly#6250) These instructions always pop a single value, except when tuples are involved, in which case they need special handling to know how many values to pop.
@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

2 participants