Lars T Hansen

Multiple instructions in one proposal packet should be OK. I think the bar should be that the instructions don't do anything "interesting" other than add new, fairly obviously useful, operations...

Off the top of my head there are at least these gating points: - new opcodes - new flags (shared-memory flag; data-section inert/active flag) - new syntax in the text...

> > In the specific case of table.fill and the ref types proposal, this would have resulted in us dropping the table.fill instruction and advancing the proposal to the next...

It's implemented in Firefox and it's been baking in Nightly for some time. What's the status of other implementations, tools, spec text? It would be nice to ship this if...

Since feature detection (for most features anyway) is currently only possible from the host environment (via validation and selective module instantiation) and one thereafter has to do an intermodule indirect...

@dtig, nice find. That's probably good enough for us for the time being.

@rossberg, i agree, but it looks like we're not in real danger of running out any time soon. Meanwhile, the "unused" prefixes we had been using for some experimental work...

I could believe that I did say that, though I suspect what I had in mind was for a module to be serialized (as we serialize it now to cache...

FWIW, a workaround used elsewhere: https://searchfox.org/mozilla-central/source/toolkit/crashreporter/google-breakpad/src/common/memory_allocator.h#45

> It is possible in principle, ... Wasm has semantics for data races and mixed atomic/non-atomic accesses and partly-aliased accesses where C has only UB, so there's a fairly big...