-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
threads: change wasm32-wasi-pthread
to wasm32-wasi-threads
#381
Conversation
wasm32-wasi-pthread
to wasm32-wasi-threads
wasm32-wasi-pthread
to wasm32-wasi-threads
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense to me. Was there any feedback from the Rust compiler about the name?
No specific guidance like "we reject this name" but you can see from this comment and this discussion that the name could potentially be considered an issue. With this change I'm trying to avoid any such issues. |
After some thought, I think that we should rename the `THREAD_MODEL=posix` build to avoid confusion. Why? Though in this project the use of this target does involve pthreads, it will not be so in other standard libraries or languages (see, e.g., rust-lang/compiler-team#574). I think it would be preferable to emphasize the "threads" Wasm-level proposal and the "wasi-threads" proposal rather than the specific details of which threading API is being exposed.
b91939f
to
3124868
Compare
@sbc100, @sunfishcode: any objections? |
cc: @penzn, @alexcrichton, @yamt |
* Add a variation of wasi-sdk.cmake for pthread-using apps * Install wasi-sdk-pthread.cmake * Build wasi-libc with THREAD_MODEL=posix as well * wasi-sdk-pthread.cmake: target rename to wasm32-wasi-threads after WebAssembly/wasi-libc#381
The target was updated to wasm32-wasi-threads in wasi-libc (and most likely will stay like that for a while) WebAssembly/wasi-libc#381
The target was updated to wasm32-wasi-threads in wasi-libc (and most likely will stay like that for a while) WebAssembly/wasi-libc#381
…sembly#381) * Change `wasm32-wasi-pthread` to `wasm32-wasi-threads` After some thought, I think that we should rename the `THREAD_MODEL=posix` build to avoid confusion. Why? Though in this project the use of this target does involve pthreads, it will not be so in other standard libraries or languages (see, e.g., rust-lang/compiler-team#574). I think it would be preferable to emphasize the "threads" Wasm-level proposal and the "wasi-threads" proposal rather than the specific details of which threading API is being exposed. * fix: rename the `expected` output directory as well
After some thought, I think that we should rename the
THREAD_MODEL=posix
build to avoid confusion. Why? Though in this project the use of this target does involve pthreads, it will not be so in other standard libraries or languages (see, e.g., rust-lang/compiler-team#574). I think it would be preferable to emphasize the "threads" Wasm-level proposal and the "wasi-threads" proposal rather than the specific details of which threading API is being exposed. I also think it would be good to settle on the name now before this gets exposed in wasi-sdk (WebAssembly/wasi-sdk#287).