Andrew Brown

I should mention: @rossberg and @binji have discussed this indirectly in #66.

> SIMD is still a fair way from standardisation Yeah, it does makes sense to wait until that happens. I guess we could leave this open to remember the discussion...

I'm also interested in attending.

@daxpedda, last year we got approval to add a new target, `wasm32-wasi-threads`, to `rustc`: https://github.com/rust-lang/compiler-team/issues/574. The plan that some of us discussed at the time was to reuse `wasi-libc` to...

Sure. And, yeah, `navigator.hardwareConcurrency` is what I'm getting at with `max-parallelism`; "concurrency" is the right term to use here, though, so I'm going to edit the issue description to read...

> if module A calls a function imported from module B and the function calls `wasi_thread_spawn`, which module is it? I don't think the "multiple linked modules" story is completely...

@yamt, can we close this now?

@sunfishcode and I had talked some time ago about switching the WASI paradigm from "export the memory" to "import the memory." It might break some things but I would recommend...

> Interesting point regarding cleanup. Presumably pthread_exit could do any needed cleanup prior to calling wasi_thread_exit. Oh, great point! They're both on the libc side so both places can have...

I am leaning in favor of `wasi_thread_exit` at this point. I share @loganek's concerns about adding to the API unnecessarily and too early but I think it is rather fundamental...