-
Notifications
You must be signed in to change notification settings - Fork 35
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
Clarify how exception identity is tracked #242
Comments
aheejin
added a commit
to aheejin/exception-handling
that referenced
this issue
Jan 6, 2023
This basically does the "handwaving" we discussed in WebAssembly#218. I think adding a concept of a backing store through backdoors in the core spec is not very feasible, so this is what we can do practically at this point. Hopefully resolves WebAssembly#242.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See the discussion in #218. The JS API spec assumes that the core spec will keep track of some opaque data as exceptions are traced through the WebAssembly execution. The most readable solution would be to explicitly handle this in the core specification, but @rossberg would prefer monkeypatching from the JS API spec.
The text was updated successfully, but these errors were encountered: