KarlSchimpf
KarlSchimpf
Good point. I will add another section outlining ideas on this. Withing WebAssembly I intentionally left exceptions opaque to limit the assumption on the environment it runs in. However, when...
In my experimental implementation of this in v8, I am handling this issue by writing the exception values thrown into a (JS) typed array of 16-bit values. This allows the...
I agree that zero-cost exceptions are the long-term goal. I didn't want to add it to the document because I thought it was a distraction from the primary concern of...
Note that exceptions are opague. Hence, you can't save it in a local variable. However, since (Wasm origin) exceptions are a tuple of values that are pushed back on the...
I agree that the meaning of what happens if uncaught should not be (necessarily) termination. Rather it should be defined by the host for which the WebAssembly module is embedded....
I agree with @rossberg-chromium that one can implement the concept, but it requires an "artificial" throw in the try body. I think a better solution is to define a second...
Would it be ok to consider a `try inst* finally' inst* end` (as I suggested above) to be a _future_ feature? Or, do you feel that this must be baked...
Marked as (future) enhancement to this proposal.