Andreas Rossberg

The ESM integration gives the illusion of cyclic linking by wrapping JS stubs around Wasm exports that don't yet exist. But they throw if invoked too early. Only once the...

@littledan: > that ended up being complex and unworkable. So these stubs do not exist in the current proposal. Ah, okay, is it just uninitialised "live" bindings then? Either way,...

Yes, tag definitions are "generative", i.e., allocated anew with each instantiation of a containing module. You are right that this is not something .wast can observe right now, which is...

@yamt, @tlively, I created a respective [PR](https://github.com/WebAssembly/spec/pull/1796) (against the wasm-3.0 branch). It implements the script extension and adds a test for generativity of instantiation. PTAL.

Yes, that would be relatively easy to add. It would even be a non-breaking change, since we allow shadowing of labels, so existing code like ``` (func $f (block $f...

Given that he proposed it, I'd suggest @zapashcanon also presents it. Happy to review a PR as well. :)

This is very useful. **Feature Sets**: I would have a very strong preference for only making large feature sets optional, for the reasons described. Ultimately, we will need to decide...

@cretz, it is going to be a fact of life that some environments won't or can't support certain features (e.g., we already know for sure that blockchain environments cannot allow...

@lukewagner, yes, I'd prefer to be precise enough to rule out any incompatibilities. Good question how. It's hard to predict what exactly will be needed, but I'm hoping that it...

I don't think you want to clutter validation with this in the spec. It should be possible to nicely decouple it by just defining what syntax is (dis)allowed. That can...