Tracking Issue for `unchecked_disjoint_bitor`
Open
Nobody has claimed this yet.
C-tracking-issue
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(disjoint_bitor)]
This is a tracking issue for the unchecked_disjoint_bitor method on integer types (and the associated intrinsic implementing it).
This is a method for cases where a | b and a + b return the same value, named after the disjoint flag in LLVM.
ACP: https://github.com/rust-lang/libs-team/issues/373
Public API
impl u8/.../u128/usize {
pub const unsafe fn unchecked_disjoint_bitor(self, other: Self) -> Self;
}
Steps / History
- Implementation: #135760
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the public API description, ACP #373, and implementation issue #135760. This tracking issue is complete only when implementation, the final comment period, and the stabilization PR have all been addressed; it currently lists unresolved questions as none.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100