Implementation: #[feature(nonpoison_condvar)]
#144651
Open
+766
−269
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tracking Issue: #134645
This PR continues the effort made in #144022 by adding the implementation of
nonpoison::condvar
.Many of the changes here are similar to the changes made to implement
nonpoison::mutex
.There are two other changes here. The first is that the
Barrier
implementation is migrated to use thenonpoison::Condvar
instead of thepoison
variant. The second (which might be subject to some discussion) is thatWaitTimeoutResult
is moved up tomod.rs
, as bothcondvar
variants need that type (and I do not know if there is a better place to put it now).Related PRs
nonpoison_rwlock
implementation: Implementation:#[feature(nonpoison_rwlock)]
#144648nonpoison_once
implementation: Implementation:#[feature(nonpoison_once)]
#144653