Francis McCabe
Francis McCabe
This should be pursued on the EH repo: https://github.com/WebAssembly/exception-handling
The issue of different browsers is likely to be a temporary phenomenon. E.g., Mozilla is already working on their implementation of JSPI in Firefox.
A couple of comments: 1. We are currently in 'origin trial' for JSPI in chrome, as of Chrome M123. I don't know how that relates to Node.js: a. Is there...
There are a couple of points here: 1. The notes that Conrad references seem to focus on working group meetings, not community group meetings. 2. If the guidelines are applicable,...
I am drafting some text to more fully explain this. However, it turns out that returning multiple values (result+errorcode) from JS into wasm/C is completely non-trivial :(
I propose the following wording re exceptions: Some programming languages, such as C, do not have explicit mechanisms for handling exceptions. In addition, dealing with _foreign_ exceptions in languages that...
Or we can not change the blog post at all; given that the issues are not actually JSPI-related.
Implementing tail calls was issue #1 for the JVM, back before there was issue trackers. Never got fixed though. As it happens, if you have reliable exception handling, you can...
So, how is someone expected to dynamically pass a callback to wasm?
This is aligned with my thinking also. Likely to take longer than wasm-unsafe-eval but a new nonce-based CSP policy source (tentatively called wasm-src) is on our minds.