Andreas Rossberg

Another question would be where custom sections get specified. There likely is going to be a broad range of them, with widely varying relevance to the broader ecosystem. It probably...

I'm not sure I follow. What concrete Wasm type would be assigned to such a function? Where would you derive it from? When supplying a JS function for an import,...

> Without this the (lazy loading) dynamic linker needs to know not just names but also function signatures. That's true, but given the js-types proposal, can't the linker read it...

Don't read too much into the version number. W3C requires it for its specs. The Wasm MVP was numbered 1.0. There hasn't been another official W3C release version yet. Informally,...

@Schweinepriester, yes and no. There is some process and bureaucracy involved. :) In the future, we want to make version numbers more significant again, since they're more succinct and ease...

To be clear, this question is not primarily about type annotations, but whether block instructions should be labelled, i.e., valid as jump targets. To reiterate the historic context: There was...

Of course, the obvious scheme would be "js:" or "es:".

Note that we initially required a deterministic representation (and shortest LEB) but removed that requirement (can't find the PR right now). The reason we removed it is that it seemed...

I can see that the ability to use a switch over a variant would be desirable. But can you elaborate why this code is "unsafe and problematic" in TypeScript? How...

> Unless the receiver expects a vec null/reserved type, sending such a vector will be rejected immediately. Not quite – as @nomeata reminded me earlier in private conversation, you can...