about summary refs log tree commit diff
path: root/library/std/src/sys_common/rwlock.rs
AgeCommit message (Collapse)AuthorLines
2022-11-06std: remove lock wrappers in `sys_common`joboet-71/+0
2022-09-25Auto merge of #98457 - japaric:gh98378, r=m-ou-sebors-0/+1
make Condvar, Mutex, RwLock const constructors work with the `unsupported` impl applying this patch locally to the `rust-src` component fixes #98378 however, the solution seems wrong to me because PR #97791 didn't add any `rustc_const_stable` attribute to underlying implementations like `std::sys::unix::futex`, so I must be missing something about how const-stability is checked ... maybe the `restricted_std` feature (gate?) has an effect? fixes #98378 fixes #98293 (probably)
2022-09-19std: use `sync::RwLock` for internal staticsjoboet-60/+0
2022-06-27make Condvar, Mutex, RwLock const constructors work with unsupported implJorge Aparicio-0/+1
2022-06-20Remove lies in comments.Mara Bos-3/+3
2022-06-06Make {Mutex, Condvar, RwLock}::new() const.Mara Bos-1/+1
2022-06-06Make all {Mutex, Condvar, RwLock}::new #[inline].Mara Bos-0/+2
2022-06-03Lazily allocate+initialize locks.Mara Bos-1/+1
2022-06-03Use Drop instead of destroy() for locks.Mara Bos-6/+0
2022-04-06Rename RWLock to RwLock in std::sys.Mara Bos-18/+18
2022-03-21Move pthread locks to own module.Mara Bos-1/+1
2021-06-01Multiple improvements to RwLocksBenoƮt du Garreau-37/+83
- Split `sys_common::RWLock` between `StaticRWLock` and `MovableRWLock` - Unbox `RwLock` on some platforms (Windows, Wasm and unsupported) - Simplify `RwLock::into_inner`
2021-04-21Move `sys_common::rwlock::StaticRWLock` etc. to `sys::unix::rwlock`Christiaan Dirkx-59/+0
2021-03-14Revert "Revert "use RWlock when accessing os::env #81850""The8472-0/+59
This reverts commit acdca316c3d42299d31c1b47eb792006ffdfc29c.
2021-03-07Revert "use RWlock when accessing os::env #81850"Eric Huss-59/+0
This reverts commit 354f19cf2475148994954b6783341620c7445071, reversing changes made to 0cfba2fd090834c909d5ed9deccdee8170da791b.
2021-02-24library: Normalize safety-for-unsafe-block commentsMiguel Ojeda-2/+2
Almost all safety comments are of the form `// SAFETY:`, so normalize the rest and fix a few of them that should have been a `/// # Safety` section instead. Furthermore, make `tidy` only allow the uppercase form. While currently `tidy` only checks `core`, it is a good idea to prevent `core` from drifting to non-uppercase comments, so that later we can start checking `alloc` etc. too. Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2021-02-09split guard into read and write typesThe8472-15/+14
2021-02-08introduce StaticRWLock wrapper to make methods safeThe8472-49/+60
2021-02-07silence dead code warnings on windowsThe8472-0/+5
2021-02-07use rwlock for accessing ENVThe8472-0/+44
2020-07-27mv std libs to library/mark-0/+88