Ben Smith

@sammax unfortunately, we can't really add text syntax like that, since wabt tries to match the spec (and future proposals). The best we can hope for is using annotations for...

Maybe a proposal like that would be accepted. I think the big question is what is the expected output from a module using this text format. If we're saying that...

> We could also introduce some kind of pseudo instruction data.addr $name that gets replaced by the offset expression for that named segment, but I'm not really sure if that's...

> @binji I like that syntax, I think we would also need table-elem= or something like it for table elements, and a way to name table elements. If you think...

I'd like to help out here too! I think I'd do best as a reviewer, but perhaps could help out in other aspects as well.

Right, I don't think it was ever the intention that you could directly replace these instructions with raw futex syscalls.

This is pretty close to what is currently implemented in d8. The primary difference is that there is currently no event loop on the main thread. Instead, messages are queued:...

Yeah, the tests just spin wait. But @mtrofin pointed out that we've recently added support for using an event loop on the main thread, so perhaps we can just rework...

@lars-t-hansen No, `getMessage` isn't necessary. I added it because we didn't have event loop support in d8 at the time, but it would be better to have the API more...

> Do you really want to start all threads upfront? Would it not be possible to create them one at a time when executing a thread command? And terminate them...