Andreas Rossberg

Changed opcodes. In the future, I would appreciate if we could get away from this mode of operation where implementations unilaterally deviate from what's proposed and then retroactively declare that...

I think it's less a question of workflow than one of style and communication. When you discover conflicts between, or unresolved issues with, proposals, try to help the champions to...

I see. But this would cause a typical test to spawn dozens of workers upfront, although it probably hardly ever uses more than two or three at a time. Isn't...

@qwertie, yeah, some of these requirements aren't stated explicitly, mostly because they were kind of "obvious". But I agree it wouldn't harm elaborating more. There still are a lot of...

I don't think you want forgeable thread ids. Depending on what primitives are available for them, that would preclude secure abstractions.

Extending tables to support threads sounds good, though I'm a bit uneasy about _tying_ threads to tables. What would be the forward compatibility story? When we add a more flexible...

@AndrewScheidecker, I am wondering more about the instruction set. With a more general thread type potentially added later it would be silly to still require a table just to create...

@AndrewScheidecker, a program using a future GC extension, for example, probably has little reason to even define a linear memory.

@lukewagner, right, and I agree with the constraint, so I was wondering if it is or is not an issue for thread ids. Off-hand I don't see a need for...

@lukewagner, the first item doesn't seem tied to thread ids, does it? The data would be needed regardless of whether somebody retains an id. So I think it would be...