Tracking Issue for AtomicBool::fetch_not

[pluiedev]

Feature gate: #![feature(atomic_bool_fetch_not)]

This is a tracking issue for the method AtomicBool::fetch_not. This method performs the NOT operation on an AtomicBool,
and returns the old (un-negated) value.

Public API

// in std::sync::atomic

impl AtomicBool {
    pub fn fetch_not(&self, order: Ordering) -> bool;
}

Steps / History

• Implementation: Add fetch_not method on AtomicBool #98479
• Final comment period (FCP)
• Stabilization PR

Unresolved Questions

• None yet.

[dimpolo]

Should we consider stabilizing this?

[dtolnay]

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

atomic.fetch_not(ordering) is equivalent to atomic.fetch_xor(true, ordering).

[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.

[rfcbot]

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

[rfcbot]

The final comment period, with a disposition to merge, as per the review above, is now complete.

As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed.

This will be merged soon.

[dimpolo]

ping :)

[Urgau]

@dimpolo Feel free to send a PR stabilizing the feature. Instructions can be found here.