Tracking Issue for `Saturating` type

[kellerkindt]

This is a tracking issue for the RFC "928" (rust-lang/rfcs#928).
The feature gate for the issue is #![feature(saturating_int_impl)].

About tracking issues

Tracks progress for Saturating type analogue to #32463

Unresolved Questions

• What is the MVP for stabilization?
• What is the correct impl of Shl and ShalAssign for Saturating<signed>
  Add Saturating type (based on Wrapping type) #87921 (comment)
  Possible solution: Tracking Issue for Saturating type #87920 (comment)
  @avitex https://github.com/avitex/rfcs/blob/master/text/0000-saturating-bit-shifts.md

Steps

• implement (Add Saturating type (based on Wrapping type) #87921)
• Stabilize saturating_div (Tracking Issue for saturating_div #89381)
• Split of saturating bit shifts (Implement saturating_shl and saturating_shr on ints #103441)
• Stabilize saturating_int_impl

Implementation history

• Implementation Add Saturating type (based on Wrapping type) #87921
  • Adds struct Saturating and feature(saturating_int_impl)
• Stabilization (TODO)

[joshtriplett]

FCP for stabilizing saturating_div:
@rfcbot merge

[rfcbot]

Team member @joshtriplett has proposed to merge this. The next step is review by the rest of the tagged team members:

• @Amanieu
• @BurntSushi
• @dtolnay
• @joshtriplett
• @m-ou-se
• @yaahc

Concerns:

• saturating shifts resolved by Tracking Issue for Saturating type #87920 (comment)

Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

See this document for info about what commands tagged team members can give me.

[Amanieu]

What about the remaining unresolved question regarding the correct behavior of Shl?

[kellerkindt]

@kennytm outlined possible implementations for that (#87921 (comment)), but I am not sure what seems to be the correct implementation and I would be happy for any input in that regards.

[Amanieu]

I would like to see the situation with saturating shift clarified first before we stabilize this. There is an unsubmited RFC about this (cc @avitex) which has been discussed a bit in Zulip (1 2) but without coming to a conclusion.

@rfcbot concern saturating shifts

[kellerkindt]

Hmm, it might be a bit confusing, but I initially intended to only stabilize saturating_div (#88624) and not the whole Saturating type (yet).

@joshtriplett also mentioned it that way here?

[Amanieu]

Oh right, I missed that message. TBF it's a bit confusing to have two very different features sharing the same tracking issue.

@rfcbot resove saturating shift