Coerce result of void functions to None & remove host_eval#128
Merged
Coerce result of void functions to None & remove host_eval#128
host_eval#128Conversation
Member
|
lgtm |
rossberg
added a commit
that referenced
this pull request
Oct 13, 2015
Coerce result of void functions to None & remove `host_eval`
Connicpu
pushed a commit
to Connicpu/wasm-spec
that referenced
this pull request
May 11, 2020
rossberg
pushed a commit
that referenced
this pull request
Feb 11, 2021
ngzhian
pushed a commit
to ngzhian/spec
that referenced
this pull request
Nov 4, 2021
dhil
pushed a commit
to dhil/webassembly-spec
that referenced
this pull request
Mar 2, 2023
This updates the explainer text according to the new spec we agreed in the 09-15-2020 CG meeting and discussions afterwards. The following are modifications and clarifications we made after the 09-15-2020 CG meeting, and the relevant issue posts, if any: https://github.com/WebAssembly/meetings/blob/master/main/2020/CG-09-15.md - `catch_br` wasm renamed to `delegate` (WebAssembly#133) - `rethrow` gains an immediate argument (WebAssembly#126) - Removed dependences on the reference types proposal and the multivalue proposal. The multivalue proposal was previously listed as dependent because 1. `try` is basically a `block`, so it can have multivalue input/output 2. `br_on_exn` can extract multiple values from a `block`. We don't have `br_on_exn` anymore, and I'm not sure 1 is a strong enough reason to make it a dependence. - Mention `rethrow` cannot rethrow exceptions caught by `unwind` (WebAssembly#142 and WebAssembly#137) - Mention some runtimes, especially web VMs, can attach stack traces to the exception object, implying stack traces are not required for all VMs - Update label/validation rules for `delegate` and `rethrow` (WebAssembly#146) - Finalize opcodes for `delegate` (0x18) and `catch_all` (0x19) (WebAssembly#145 and WebAssembly#147) I believe this resolves many previous issue threads, so I'll close them. Please reopen them if you think there are things left for discussions in those issues. Resolves WebAssembly#113, resolves WebAssembly#126, resolves WebAssembly#127, resolves WebAssembly#128, resolves WebAssembly#130, resolves WebAssembly#142, resolves WebAssembly#145, resolves WebAssembly#146, resolves WebAssembly#147.
stevenfontanella
pushed a commit
to stevenfontanella/spec
that referenced
this pull request
Nov 12, 2025
Update repos:
spec:
WebAssembly@1041527
exception-handling:
WebAssembly/exception-handling@af287a7
gc:
WebAssembly/gc@756060f
function-references:
WebAssembly/function-references@74d2ec8
This change was automatically generated by `update-testsuite.py`
Co-authored-by: WebAssembly/testsuite auto-update <github-actions@users.noreply.github.com>
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.
Fixes #122.
The
host_evalfunction breaks onceNoneresults are coerced, so I had to remove it for good. Only const nodes are still allowed as arguments to asserts (I also looked for ways to introduce a leaner assert syntax while at it, but the explicit type info from the const opcodes is still needed, so I left it as is for the time being).Also did a few stylistic clean-ups.