Tracking Issue for `get_set_bit`

Feature gate: #![feature(get_set_bit)]

This is a tracking issue for adding getters and setters of individual bits to all integral types.

Public API

This feature simplifies working with bitflags by adding to each integral type

• a bit method retrieving whether the bit at some index (0 is the least significant bit) is set, and
• a set_bit method for creating a new number, obtained form the old number by setting a specific bit to either zero or one.

impl /* u8 u16 u32 u64 u128 usize i8 i16 i32 i64 i128 isize */ {
    pub const fn bit(self, index: u32) -> bool;
    pub const fn set_bit(self, index: u32, value: bool) -> Self;
}

Steps

• ACP: https://github.com/rust-lang/libs-team/issues/667
• Implementation: https://github.com/rust-lang/rust/pull/147696
• Final comment period (FCP)^1
• Stabilization PR

Unresolved Questions

• Name of the setter might change to with_bit_set or simply with_bit to indicate more clearly that the setter creates an independent copy. See https://github.com/rust-lang/rust/pull/147696#issuecomment-3403219732

Start by reviewing the ACP and the implementation PR linked in the issue, then check the unresolved setter-naming question. The tracking work is complete only after the implementation, final comment period, and stabilization PR have progressed; this issue is already being handled elsewhere.