Andreas Rossberg
Andreas Rossberg
Alternatives to i31ref wrt compiling parametric polymorphism on uniformly-represented values (OCaml)
@aardappel: > I don't see why generic functions that are not used in this very dynamic fashion (which I would certainly hope are the vast majority) should suffer from the...
Hm, that would be really odd. All existing table/memory/global instructions have the respective entity index in plain form. For example, we don't write `get (table $x)` and `get (global $x)`...
@Pacerier, the availability of GC in Wasm won't affect code that doesn't use it. In particular, the GC'ed heap will be completely separate from the linear memory. Basically, all that's...
Fair enough. Conceivably, the specification for a future Wasm with GC could identify a GC-free sublanguage that implementations can choose to restrict to.
@kripken, yes, up to some renaming and minor tweaks.
@taralx: > `cont.throw` doesn't take an `evtref`, so it's not possible to respond to an unknown suspension with an exception. Is that intentional? That's a good point. But you cannot...
@RossTate: >> It does, and more importantly, it does so in a composable fashion -- an important point I forgot to include (added). I.e., you can use multiple of these...
Updated OP to match the version I presented today, removing separate evtref type and br_on_evt instruction. Also removed cont.forward instruction, since it may not be needed and its semantics seems...
Yeah, I suspect that we won't even be able to pass simple data references between threads for quite some time to come, let alone functions or stacks. The hurdle isn't...