Tracking Issue for `try_from_int_error_kind`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(try_from_int_error_kind)]
This is a tracking issue for the kind method on TryFromIntError, and the NotAPowerOfTwo variant on IntErrorKind.
The kind method outputs the detailed cause of converting an integer failing.
The NotAPowerOfTwo variant is required for TryFrom<usize> for Alignment.
Public API
// core::num
impl TryFromIntError {
pub const fn kind(&self) -> &IntErrorKind;
}
pub enum IntErrorKind {
...
// For `TryFrom<usize> for Alignment`.
NotAPowerOfTwo,
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP: rust-lang/libs-team#746
- Implementation: #153178
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- Which would be better for the return type:
IntErrorKindor&IntErrorKind?
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 public API signatures for TryFromIntError::kind and IntErrorKind::NotAPowerOfTwo, then inspect implementation PR #153178. Resolve the listed return-type question and follow the FCP and stabilization checklist; completion is a stabilization PR after those steps.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100