Andreas Rossberg

It is intentional. I can't find the original discussion right now, but being able to pass exception packages as first-class values to JS would have nasty implications, such as: -...

Indeed, the spec does not care either way. Since stack traces are only observable in JS, the core Wasm spec is agnostic to them. But even JS does not specify...

@Ms2ger, well, that's exactly what I'm suggesting, though: by exposing it as an externref, we'd naturally assign it such an address, and nothing else would be needed (AFAICS).

IIRC, the problem (reported by @matthias-blume at the time) was that implementing the right behaviour for invalid function pointers when "safely" compiling something like C required manual bounds checks in...

> Given the late stage of the proposal, this change should be confirmed with a pre-announced vote in the CG. Just want to note that this isn't a change, merely...

I totally understand the desire, but is it really worth going down that road just yet? The text format isn't meant to be written by hand at a larger scale....

Hm, I'm not sure I follow that argument. I could see us caring about code size numbers if we were talking about a transport format. But the text format isn't...

The proposal is "live" already, in the sense that most major engines have shipped it for quite a while. The spec bit you link has no direct relation to this...

FTR, I made the [same observation](https://github.com/rossberg/dummy/pull/1#discussion_r1408064110). If you want WIT to scale, then there really ought to be a declaration form for naming interface types. (And as Luke is aware,...

Yes. This assumes that all arrays will forever pay the cost for carrying complete runtime type information, which is an assumption that I'd absolutely like to avoid. As a ground...