Tracking Issue for mutex_unpoison

[tmccombs]

Feature gate: #![feature(mutex_unpoison)]

This is a tracking issue for functions to clear the poisoned flag on Mutex and RwLock.

Public API

// std::sync

impl<T: ?Sized> Mutex<T> {
    pub fn clear_poison(&self);
}

impl<T: ?Sized> RwLock<T> {
    pub fn clear_poison(&self);
}

Steps / History

• https://internals.rust-lang.org/t/unpoisoning-a-mutex/16521
• Implementation: Add functions to un-poison Mutex and RwLock #96422
• Final comment period (FCP)
• Stabilization PR

Unresolved Questions

• None yet.

[GilShoshan94]

Hi,

I read https://internals.rust-lang.org/t/unpoisoning-a-mutex/16521/3 (wich got automatically closed by the way) and the PR #96422.
It seems all good.

What is the next step to make it in the stable API ? Can I help somehow ?

[randommm]

Hi, sorry if flooding but are there any updates regarding this issue?

[tmccombs]

I think the next step is one of the rust developers needs to start the final comment period. IDK what the criteria for doing so are.

[dtolnay]

@rust-lang/libs-api:
@rfcbot fcp merge

https://doc.rust-lang.org/nightly/std/sync/struct.Mutex.html#method.clear_poison
https://doc.rust-lang.org/nightly/std/sync/struct.RwLock.html#method.clear_poison

[rfcbot]

Team member @dtolnay has proposed to merge this. The next step is review by the rest of the tagged team members:

• @Amanieu
• @BurntSushi
• @dtolnay
• @joshtriplett
• @m-ou-se

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.

[BurntSushi]

I was wondering whether the idea of putting this method on the guard had been considered and found that @m-ou-se's commentary (and the ensuring comments) addressed it. SGTM!

[rfcbot]

🔔 This is now entering its final comment period, as per the review above. 🔔