Tracking Issue for const_ops
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(const_ops)]
This is a tracking issue for const-stability of traits in ops.
Public API
// core::ops
#[const_trait]
pub trait Add<Rhs = Self> { ... }
#[const_trait]
pub trait Sub<Rhs = Self> { ... }
#[const_trait]
pub trait Mul<Rhs = Self> { ... }
#[const_trait]
pub trait Div<Rhs = Self> { ... }
#[const_trait]
pub trait Rem<Rhs = Self> { ... }
NegNotBitAndBitOrBitXorShlShrAddAssignSubAssignMulAssignDivAssignRemAssignBitAndAssignBitOrAssignBitXorAssignShlAssignShrAssign
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- Implementation:
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions / Blockers
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 with the core::ops traits listed in the issue and review implementation PRs 143000, 143040, and 143949. Check the blocker in issue 143874 and the feature-lifecycle guidance before assessing the remaining stabilization work. Done means the unresolved blocker is addressed, the final comment period is complete, and a stabilization PR is merged.
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
- 20/100