Derek Schuff

Another way to think about this is to ask, which is better: 1. Start with an assembly language, and turn it into a Wasm assembly language. This means adding mnemonics...

Just having a text representation of the instructions (and in the case of GC, of types) is a pretty small deal compared to, for example, actually having meaningful support for...

Yeah, that looks pretty straightforward, it seems like it could work pretty similarly to how we trigger release updates between emsdk and emscripten today.

Agreed that this would be nontrivial. I'll also add thought that something like this would be useful for importing wasm tests into WPT (Web Platform Tests). We currently have automation...

I've actually also been thinking about this lately, in the context of importing spec tests into WPT. WPT also likes to have functionality organized by "feature" and of course browsers...

I took a shot at separating the memory instructions, because not all implementations support memory64 and/or multi-memory yet (even major ones), and I could easily imagine use cases where an...

#1964 is (I think) now complete for splitting bulk-memory, memory64, and multi-memory, which are related enough that it seems like a reasonable test. The PR is fairly straightforward, although it...

I totally agree that from a purely spec-focused perspective, the order of feature standardization, and the order of implementation (in engines that do intend to support them) is somewhat arbitrary....

Thanks for flagging this! I probably won't be able to get to this myself until next week, but I should be able to review if you want to send a...

We discussed this a bit offline, but for the record, when you use the token here, the actions should be done with the permissions of @emscripten-bot (so the fact that...