Tracking Issue for sync_nonpoison
and nonpoison_{condvar,mutex,once,rwlock}
#134645
Labels
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
E-hard
Call for participation: Hard difficulty. Experience needed to fix: A lot.
E-help-wanted
Call for participation: Help is requested to fix this issue.
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
Feature gates:
#![feature(sync_nonpoison)]
#![feature(nonpoison_condvar)]
#![feature(nonpoison_mutex)]
#![feature(nonpoison_once)]
#![feature(nonpoison_rwlock)]
This is a tracking issue for versions of synchronization primitives that do not not need to worry about poison.
Public API
sync_nonpoison
The module itself and common types will be gated by this feature:
nonpoison_condvar
nonpoison_mutex
nonpoison_once
nonpoison_rwlock
Steps / History
Unresolved Questions
Related
std::sync::poison
and reexport them Tracking Issue forsync_poison
#134646ReentrantLock
currently does not support poisoning Tracking Issue forReentrantLock
#121440mapped_lock_guards
adds API to the guard types Tracking Issue formapped_lock_guards
(MappedMutexGuard
,MappedRwLockReadGuard
,MappedRwLockWriteGuard
) #117108Footnotes
https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩
The text was updated successfully, but these errors were encountered: