rust/library/std/src/sys/sync, branch stablehttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=stable2025-07-13T10:37:34+00:00Add comment why we use zero for COMPLETE2025-07-13T10:37:34+00:00Orson Petersorsonpeters@gmail.com2025-07-13T10:37:34+00:00urn:sha1:f041962694875c0f0a33f8a5e27fd00597042169Use zero for initialized Once state2025-07-13T10:16:40+00:00Orson Petersorsonpeters@gmail.com2025-07-13T10:16:40+00:00urn:sha1:a2d41393365df0c0c9f728de7f79b8f0d4e14ef2Add comments to diagnostic items2025-05-28T15:05:45+00:00Patrick-6pamu99@gmx.ch2025-05-28T15:05:45+00:00urn:sha1:8237107d88866d4f4525f77384c653d4c80ad4dfMake pthread Mutex internals less public2025-05-28T13:13:38+00:00Patrick-6pamu99@gmx.ch2025-05-28T13:13:38+00:00urn:sha1:149b5b2567535af761d16ed388b653740db7a457Add diagnostic items to sys::Mutex2025-05-28T13:12:56+00:00Patrick-6pamu99@gmx.ch2025-05-28T13:12:56+00:00urn:sha1:2e99a880e22f5a1f3800e1a26828b188204d037ecollect all Fuchsia bindings into the `fuchsia` module2025-05-05T10:16:40+00:00joboetjonasboettiger@icloud.com2025-05-05T10:16:40+00:00urn:sha1:7845c011dd3bdfb5eaa461476f5f7d0f3aa16dfc
The Fuchsia bindings are currently spread out across multiple modules in `sys/pal/unix` leading to unnecessary duplication. This PR moves all of these definitions into `sys::pal::unix::fuchsia` and additionally:
* deduplicates the definitions
* makes the error names consistent
* marks some extern functions as safe
* removes unused items (there's no need to maintain these bindings if we're not going to use them)
* removes the documentation for the definitions (contributors should always consult the platform documentation, duplicating that here is just an extra maintenance burden)
use generic Atomic type where possible2025-04-26T23:18:08+00:00Christopher Durhamcad97@cad97.com2024-09-19T04:15:03+00:00urn:sha1:4d93f6056824c338751f19356d33bb61ce818749
in core/alloc/std only for now, and ignoring test files
Co-authored-by: Pavel Grigorenko <GrigorenkoPV@ya.ru>
Fix `*-win7-windows-msvc` target since 26eeac1a1e9fe46ffd80dd0d3dafdd2c2a6443062025-02-19T10:05:37+00:00Li Keqingauroracloud4096@gmail.com2025-02-19T10:05:37+00:00urn:sha1:35febd7a6d57179f41cb5b4a37f9545915e4d7a5Mark extern blocks as unsafe2025-02-09T17:11:13+00:00Michael Gouletmichael@errs.io2025-02-07T19:42:33+00:00urn:sha1:a4e7f8f9bf10588cb5519ae09a15be155499901fRollup merge of #134389 - rust-wasi-web:condvar-no-threads, r=m-ou-se2025-01-08T05:52:45+00:00Jacob Prattjacob@jhpratt.dev2025-01-08T05:52:45+00:00urn:sha1:5ed1fa84a50d6af682fbd3c1d0b455e87f959924
Condvar: implement wait_timeout for targets without threads
This always falls back to sleeping since there is no way to notify a condvar on a target without threads.
Even on a target that has no threads the following code is a legitimate use case:
```rust
use std::sync::{Condvar, Mutex};
use std::time::Duration;
fn main() {
let cv = Condvar::new();
let mutex = Mutex::new(());
let mut guard = mutex.lock().unwrap();
cv.notify_one();
let res;
(guard, res) = cv.wait_timeout(guard, Duration::from_secs(3)).unwrap();
assert!(res.timed_out());
}
```