Marcin Kolny

> i feel it's simpler to make them arguments of wasi_thread_spawn Yeah, that was the option I suggested https://github.com/WebAssembly/wasi-threads/issues/12 but I didn't really like it so I asked others for...

Hi, sorry for late reply. > Your top post here says that VMs may implement the stack check. That suggests that you're proposing a change to the module-engine ABI. Is...

> I know you mention some rational in https://github.com/WebAssembly/wasi-libc/issues/322, but I'm curious what you personal primary motivation is for wanting to make this change? Pretty much what @penzn already mentioned...

> Could you add some instructions (maybe as a mod to the README) so I can try it out? I've love to give it go. Does this setup support out-of-tree...

Yes, incremental build is a huge benefit, but I never listed it as a benefit because I'm not sure how hard is it to implement it for the existing Makefile.

Thanks a lot for the reply. I see the concern you raised about the values matching Linux's values. My preference would be to keep the code as close to the...

Having another syscall for exiting the thread sounds reasonable. Also, I agree with @sbc100 about keeping the API simple and move as much of the implementation as possible to WASM...

> @loganek do you think being able to exit a thread without unwinding the stack is critical? What do you think about simply not implementing `pthread_exit` at all? @sbc100 I'm...

Thanks @yamt , I was more interested in real usecases than just a number of occurrences of a specific function on github - i.e. do we know for sure that...

I'm leaning towards not implementing this function for now, and only add it when somebody comes with a usecase where the existence of it either is absolutely necessary or greatly...