Skip to content

Tracking Issue for unchecked_disjoint_bitor #135758

Description

@scottmcm

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: rust-lang/libs-team#373

Public API

impl u8/.../u128/usize, i8/.../i128/isize, bool {
    pub const unsafe fn unchecked_disjoint_bitor(self, other: Self) -> Self;
}

Steps / History

Unresolved Questions

  • None yet.

Footnotes

  1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

Activity

  1. added
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    T-libs-api[DEPRECATED; DO NOT USE]
    on Jan 20, 2025
  2. clarfonthey commented on Jun 4, 2025

    @clarfonthey
    Contributor

    Are there any major impediments to stabilising this, since it's been over four months?

  3. bjoernager commented on Oct 5, 2025

    @bjoernager
    Contributor

    Additional implementations for bool and signed types: #147368.

  4. added
    T-libsRelevant to the library team, which will review and decide on the PR/issue.
    and removed
    T-libs-api[DEPRECATED; DO NOT USE]
    on Aug 12, 2026
  5. added a commit that references this issue on Oct 23, 2026
  6. added a commit that references this issue on Oct 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libsRelevant to the library team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions