| 04:43 | <bakkot> | https://github.com/oven-sh/WebKit/pull/249 |
| 08:03 | <Ashley Claymore> | Wouldn't this require all MOP ops to be thread safe. Which sounds like it would add some overhead |
| 08:54 | <Mathieu Hofman> | I'm pretty sure the spec doesn't allow the implementation to actually do this. |
| 08:59 | <Ashley Claymore> | Personally I'm still hoping for https://github.com/tc39/proposal-structs and being able to start a worker using import source |
| 20:25 | <Mathieu Hofman> | I'm pretty sure the spec doesn't allow the implementation to actually do this. I suppose that nothing specifies that the memory backing non shared data blocks cannot be accessed by concurrent agents, but pretty much all spec algorithms assume there is no concurrent agent access. The thing is Moddable actually does have multiple agents running on the same Realm, but the only shared objects are deeply and transitively immutable, so any mutable memory is still per agent and not shared. I think we should have an explicit invariant similar to the liveness one that defined observable garbage collection so that a host can only create agents such that a program in a single agent can only observe an execution as if there was no other agent running concurrently (notwithstanding shared array buffer) |