rust-lang / rust-lang/rust

Tracking Issue for integer extension and truncation methods

Open
#154,330 28 comments 16 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue S-tracking-needs-to-bake T-libs
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

View all comments

Feature gate: #![feature(integer_extend_truncate)]

This is a tracking issue for integer extension and truncation methods.

Public API
impl iX {
    // `Target` is a signed integer with size >= Self
    fn widen<Target>(self) -> Target
        where Self: WidenTarget<Target>;

    // `Target` is a signed integer with size <= Self
    fn truncate<Target>(self) -> Target
        where Self: TruncateTarget<Target>;
    fn saturating_truncate<Target>(self) -> Target
        where Self: TruncateTarget<Target>;
    fn checked_truncate<Target>(self) -> Option<Target>
        where Self: TruncateTarget<Target>;
}

impl uX {
    // `Target` is an unsigned integer with size >= Self
    fn widen<Target>(self) -> Target
        where Self: WidenTarget<Target>;

    // `Target` is an unsigned integer with size <= Self
    fn truncate<Target>(self) -> Target
        where Self: TruncateTarget<Target>;
    fn saturating_truncate<Target>(self) -> Target
        where Self: TruncateTarget<Target>;
    fn checked_truncate<Target>(self) -> Option<Target>
        where Self: TruncateTarget<Target>;
}
Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

Unresolved Questions
  • None yet.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the integer_extend_truncate feature gate and the completed implementation in rust-lang/rust#154356. Then read the stabilization procedure linked in the final comment period section; done means completing FCP and preparing the remaining stabilization PR.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.