JF Bastien

@rossberg-chromium so you're satisfied with the definition of possible execution orders (not all the details, just its general existence), but not with the definition of agents?

I don't understand why you think this is the case. Defining possible execution orders is the harder part in my understanding, because the other agents we're talking about aren't exotic...

> Does it actually affect interop which operations are lock-free on the other side? Yes. Concretely it means that tearing can occur.

Is this something that will be proposed at the upcoming WebAssembly meeting? If so, can we get a design soon? I'd advise to keep it kinda separable so we can...

I think we'd need to rope in a group such as web performance for this.

If we can get a rough sketch and some performance information then this is worth polling at the meeting.

The question of where the canonical memory model lives, and how to share, should probably be discussed as a joint TC39 / WebAssembly thing. Dan, would you be OK listing...

I suggest designing the details of this feature and presenting this design to the CG.

It's also worth considering per-thread init versus global init.

> I think that's what this would allow ("global init" would mean you disable the segment after the first instantiation, "per-thread init" means you wouldn't disable, just pass in different...