-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Function get_name could not be found for wasm::thread::Thread #121932
Comments
rustbot
added
the
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
label
Mar 3, 2024
While playing around locally, adding this, in use crate::ffi::CString;
...
impl Thread {
...
pub fn get_name() -> Option<CString> { None }
...
} |
That looks great! Would you be willing to submit a PR? |
Definitely! |
Noratrieb
added
O-wasm
Target: WASM (WebAssembly), http://webassembly.org/
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
A-thread
Area: `std::thread`
and removed
C-bug
Category: This is a bug.
needs-triage
This issue may need triage. Remove it if it has been sufficiently triaged.
labels
Mar 3, 2024
GuillaumeGomez
added a commit
to GuillaumeGomez/rust
that referenced
this issue
Mar 3, 2024
…strieb Add missing get_name for wasm::thread. Fixing rust-lang#121932 by implementing `get_name` in `wasm::thread::Thread`.
rust-timer
added a commit
to rust-lang-ci/rust
that referenced
this issue
Mar 3, 2024
Rollup merge of rust-lang#121933 - Iansa9:thread-name-wasm-fix, r=Nilstrieb Add missing get_name for wasm::thread. Fixing rust-lang#121932 by implementing `get_name` in `wasm::thread::Thread`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Compilation of any code using the atomics feature flag for the wasm target fails when building the std library due to the following error:
I tried this code:
With these flags enabled
I expected to see this happen:
Compilation succesful
Finished dev [unoptimized + debuginfo] target(s) in 0.59s
Instead, this happened:
Meta
rustc --version --verbose
:Backtrace
Backtrace doesn't seem to add useful information.
The text was updated successfully, but these errors were encountered: