16:04:49Bikespecifically... well let me think about what would need to change...
16:06:41Bikeif i remember correctly the problem i hit was that foreign exceptions can't... nest? like you can't throw a non-C++ exception while handling one
16:06:48Bike"Nested foreign exceptions, or rethrowing a foreign exception, result in undefined behaviour. " yeah, that
16:07:11Bikeand i think the reason for that is that the chain of exceptions is stored in the __cxa_exception object instead of the non-language-specific object
16:07:31Bikei'd probably need to, like, talk to someone who works with this stuff regularly.
16:08:46Bikeand the other problem is this wouldn't actually improve performacne because exceptions would stillb e slow. right. can't forget that
16:08:58Bikei mean, it might improve it a little,b ut we'd still be parsing LSDAs and whatnot
16:32:03phoemy proposal is mostly orthogonal to exception handling because it mentions non-local control flow, and therefore it should be processed as a separate wasm proposal
16:32:08phoewith reasons like the ones I've mentioned in my post
16:32:18phoeincluding performance and lack of exception semantics in some languages
16:32:38phoeI'll edit my post to take this into account, run it by this person and by Ioanna, and then think of how to go forth with it
21:09:46mseddonphoe: that's great news! if there's any way I can help support this proposal, let me know!
21:12:48mseddonto be fair I am actually quite out of the loop on the status of the current exception handling proposal. I should probably swing by and see how that looks...
22:10:27drmeisterI would love to get clasp building to WASM
22:11:01drmeisterClasp or ECL stand the best chance of making it.
23:00:20mseddonYeah. It's a long slog, but doable.
23:00:55mseddonHuh. I hadn't considered ecl, good shout
23:03:32Bikeecl can compile lisp to C and doesn't use C++ exceptions, right? sounds like a good choice
23:03:38Bikei don't know how it does nonlocal exits. sjlj?