Thomas Lively

Let's keep this on topic. This is not an issue about EH.

> So far you have had a major user base for every feature, namely C/C++/LLVM implementors and developers. But now that's no longer case: C/C++/LLVM isn't utilizing the proposed subtyping....

I like that idea. It's very similar to an idea raised multiple times as a way to make the "web VMs" requirement more flexible and I saw that a similar...

It would definitely be useful to get input from various current proposals about what kinds of questions are asked most frequently and what the most successful organization of information has...

I'm not sure we need to list toolchains. If the maintainers of a non-toy toolchain pop up out of nowhere and say they're successfully using a proposal, that's good enough...

I agree that design feedback from code generators is important, and I broadly agree with your description of the phases, but I don't want to overstate the current problem. Most...

Good point, @lars-t-hansen. I totally agree that instructions used by low-level runtime libraries like compiler-rt should count as used by a toolchain. In that case the code generator does not...

When newcomers bring proposals to the CG I think they often do not expect to be ready for phase 1 after a single presentation or they don't know that votes...

There is pretty good high-level guidance at https://github.com/WebAssembly/meetings/blob/master/process/consensus.md#online-consensus: > When a proposal is near maturity the champion shall bring it to an in-person meeting and seek wider consensus on open...

Once we have [typed function references](https://github.com/WebAssembly/function-references) it would be neat if a JIT feature could use them. I'm picturing an instruction that takes a memory address and size and returns...