Skip to content
This repository was archived by the owner on Apr 25, 2025. It is now read-only.

Clarify how exception identity is tracked #242

Open
Ms2ger opened this issue Nov 9, 2022 · 0 comments
Open

Clarify how exception identity is tracked #242

Ms2ger opened this issue Nov 9, 2022 · 0 comments

Comments

@Ms2ger
Copy link
Contributor

Ms2ger commented Nov 9, 2022

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.
aheejin added a commit to aheejin/exception-handling that referenced this issue Jan 6, 2023
@aheejin
[js-api] Mention opaque data requirement
704bc30 
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.
@aheejin aheejin mentioned this issue Jan 6, 2023
Closed
@titzer titzer mentioned this issue Jul 24, 2023
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[js-api] Mention opaque data requirement aheejin/exception-handling
1 participant
@Ms2ger