Andreas Rossberg
Andreas Rossberg
> If it is useful to express ordering constraints relative to virtual sections that may or may not be present in the binary module, then it must be worthwhile to...
From first glance, this looks like a plausible change. But I probably won't have time to look into it for a week or two. It means a few more conditions...
I created #99, which would relax the semantics as suggested. It's not hard but a moderate complication, so we should be perhaps be discussing whether it's worth it.
I just noticed that this issue is still open. @tlively, is this still relevant for Binaryen?
> There should probably be a test for this situation, ideally eventually upstream in the spec tests. @keithw, PTAL at [this spec PR](https://github.com/WebAssembly/spec/pull/1725).
``` some_check if return end ``` You should be able to shorten that `if return end` even more to just `br_if i`, where `i` is the label of the function...
Perfect, I like it! Thanks for looking into this. Will do a code review on #19.
I agree that roll-your-own GC is going to remain an important use case. With regard to built-in support for stack walking, however, nobody has put in the effort of proposing...
The core spec doesn't have any notion of exception identity – we removed that intentionally, otherwise we could have kept `exnref`. To model such an identity, you'll basically have to...
I agree that it would be odd not to support this. The length-type-is-the-min-of-both-index-types part is slightly ugly, but still okay.