Tracking Issue for NonZeroUn::is_power_of_two (feature nonzero_is_power_of_two)

[scottmcm]

Feature gate: #![feature(nonzero_is_power_of_two)]

This is a tracking issue for NonZeroUsize::is_power_of_two (and friends for the other unsigned types).

Like NonZeroUsize::leading_zeros (#79143), this generates simpler code than the underlying integer type because it can avoid a separate zero check.

Public API

impl NonZeroUsize {
    pub fn is_power_of_two(self) -> bool;
}

// And also for NonZeroU8, NonZeroU16, ...

Steps / History

• Implementation: Add NonZeroUn::is_power_of_two #81107
• Final commenting period (FCP)
• Stabilization PR

Unresolved Questions

• None yet.

[scottmcm]

With NonZeroU#::leading_zeros stabilized, I would like to propose NonZeroU#::is_power_of_two for stabilization as well.

(I think this in the tracking issue is the right thing to do now, rather than filing a PR?)

[joshtriplett]

@rust-lang/libs-api, shall we stabilize NonZeroU*::is_power_of_two?

@rfcbot merge

[rfcbot]

Team member @joshtriplett 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
• @yaahc

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.