Andreas Rossberg

Wasm implementations indeed use chained segmented stacks to represent continuations. But unfortunately, that does not eliminate the need for copying. As soon as you have stack-allocated mutable state, which is...

@titzer, isn't that assuming that no host function ever calls back into Wasm?

We have already planned ahead for allowing multiple table _indices_. In particular, some of the late changes to the binary format made sure that every instruction related to memory has...

This simply verifies that (ref.null any) and (ref.null none) are the same value. There is no type matching involved, neither dynamically nor statically (the script level is pretty much untyped).

Well, both variants of the null instructions produce the same null value. There exists only one null value (per type hierarchy anyway, across hierarchies they are incomparable so you can't...

The type exnref is defined to be a shorthand for (ref null exn) by the core spec. But it may be worth expanding it out explicitly here. The same probably...

@skuzmich: > Wasm GC was almost exclusively designed to accommodate efficient interop with JS and browser I'm curious what gave you that idea, because that was at most a secondary...

@littledan, a race to the top is usually a good thing when it comes to arbitrary limits. Every language implementation has tons of implicit limitations, almost no language even documents...

I agree with @waterlens. Bignums are a feature of various languages these days, and libraries like GMP or LibTomMath are used in many other cases as well. It would be...

A few drive-by comments: 1. The even bigger reason that there are no canonical choices of type definitions to lower to are subtyping declarations, which the comment layer cannot guess....