Ben L. Titzer

Like I said, names don't matter to engines, so their uniqueness doesn't matter to engines either. They matter to _linkers_, so it's a particular linking solution's choice if it wants...

This is exactly the problem that took me so long to face. Modules do *not* have types without considering the import processor that gives meaning to the names and constraints...

Virtualization is important, and programmable linking should surely support that. I actually don't think what I am talking about is very different from today's wasm, and what I am talking...

Having implemented dead code validation in multiple engines and having participated in the history of this unfortunate topic from the beginning, I'll just heave a sigh here first. There were...

@conrad-watt If I read your proposal right, that would just mean that push() is a no-op if the top of the control stack is marked as unreachable, correct? If so,...

> When "an instruction that ends control flow" (ref. your post) is encountered, validation empties/discards the current control block's type stack, skips to the end of the block, pushes the...

> The type annotations are only "missing" to the extent that they facilitate the current typing approach. Well, type annotations are like violence; if they aren't working, it's because you're...

For more context here: V8's compilation model completely changed in the 3+ years from MVP to now. Originally it did full specialization of code to even the memory start/size of...

+1 to what @dschuff says here. It looks like it'd be easy to make a case for byte-swap instructions.

We did discuss shrinking memory in the initial design of Wasm memories. This is a really tricky area in the internal implementation inside of engines. In particular, shrinking a memory...