Implement renaming of "events" to "tags" in Wasm exceptions proposal
Categories
(Core :: JavaScript: WebAssembly, enhancement, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox92 | --- | fixed |
People
(Reporter: asumu, Assigned: asumu)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
There has been a spec discussion of whether to rename the concept of "events" in the Wasm exception handling proposal (https://github.com/WebAssembly/exception-handling/issues/159) and consensus seems to be to rename them to "tags".
(The motivation behind "tags" is to use a generic enough name that it can be used for other future proposals while avoiding confusion with other concepts called "events" in JS)
There are pull requests to implement this change in the spec, LLVM, and binaryen: https://github.com/WebAssembly/exception-handling/issues/159#issuecomment-863099331
This bug is for handling this change in SpiderMonkey.
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
•
|
||
My plan was to initially leave text format tests as-is (except for changing error messages where needed) and just implement the change for the engine until the renaming is also implemented in wasm-tools/wat.
Assignee | ||
Comment 2•4 years ago
|
||
The Wasm exception handling spec has changed to rename "events"
to "tags". As a result, WebAssembly.Exception
gets renamed
to WebAssembly.Tag
and WebAssembly.RuntimeException
becomes
WebAssembly.Exception
.
Assignee | ||
Comment 3•4 years ago
|
||
The concept of "events" in the Wasm exception handling proposal
has been renamed to "tags". This commit implements this renaming
in most cases (an exception is text format tests).
Depends on D118281
![]() |
||
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 4•4 years ago
|
||
There are some r+ patches which didn't land and no activity in this bug for 2 weeks.
:asumu, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee | ||
Comment 5•4 years ago
|
||
This patch is just waiting to land and the delay is mostly just due to timing. It's been recently rebased and still relevant, so I'll clear the needinfo.
Comment 7•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/49a2b786ffb3
https://hg.mozilla.org/mozilla-central/rev/41ea9227d3e6
Description
•