Heejin Ahn

@Ms2ger Again, I'm not sure what the relationship between the commit you referenced and this issue?

I don't think the spec forces eager stack tracing, and the embedder may or may not embed a stack trace based on its preference. But I acknowledge that if the...

> Because the exnref can be stored, it can be rethrown from a place with a different stack. So mutating the exnref' would give you a stack trace that's a...

> > Also I don't know much about .NET's primitive instructions on exception handling, so I'm not sure if what they're doing can be applied to us. I'd appreciate if...

I briefly checked how .NET supports general C++ `throw;`, which can occur anywhere including function calls, with the `rethrow` primitive only permitted within `catch` blocks as you said, and it...

I haven't managed to read all of your last comment yet, and I have to go now for today (I'm in a different timezone now), but I forgot to mention...

> Nice find! And thanks to the link to EHScheme.md; it's so far been easy to follow (though I can't say I've managed to read it all yet). > >...

I don't think we have any clear idea on what you mean by "something closer to .NET" in the first place. As I said, .NET has a kind of weird...

> Here are the three most important steps: > > 1. Exceptions are only reified when caught (e.g. no `exnref` provided when just executing destructors or finally clauses) What's the...

> No. If you're still in the catch clause, you can still use rethrow. Isn't `rethrow` supposed to generate stack traces as it goes on? Are we gonna tell `rethrow`...