Andreas Rossberg

Thanks, I left a few more replies.

@dschuff, what's the status of this PR?

The tag type essentially works as a cross-site type annotation, so all local types ought to be subtypes of that to agree. So yes, it should be `t2*

I think what you are describing is what's usually called *named handlers*. There is a [sketch](https://github.com/WebAssembly/stack-switching/blob/main/proposals/continuations/Explainer.md#named-handlers) of how that could look with typed continuations in the explainer. (What we previously...

As noted on #1989 ([comment](https://github.com/WebAssembly/spec/pull/1989#issuecomment-3349049939)), the situation is worse: some of the items in the current JS API spec actively violate the core spec! This leads to JS engines failing...

@eqrion, good point, but I agree: it doesn't look like that solution is dependent on the limit being a validation time error, instantiation time would work as well.

Just repeating my usual observation that allowing cycles is much more than a mere API addition. It would introduce full-fletched recursive modules into Wasm, which is a tricky design space...

@lukewagner, the dynamic module system I developed in my thesis (a long time ago...) defined its semantics for lazy linking in a similar manner, based on proper futures. :)

@lukewagner, yes, it's just a way to be able to "provide" the dependencies before you "have" them, so that e.g. compilation can proceed and parallelism can be maximised. The actual...

Even if we were to relax this, we would need to fix a behaviour in deterministic mode, which some platforms have a hard reliance on. Is the only solution for...