stabilize new RangeToInclusive type

[pitaj]

stabilizes core::range::RangeToInclusive

// in core::range

pub struct RangeToInclusive<Idx> {
    pub last: Idx,
}

impl<Idx: fmt::Debug> fmt::Debug for RangeInclusive<Idx> { /* ... */ }

impl<Idx: PartialOrd<Idx>> RangeToInclusive<Idx> {
    pub const fn contains<U>(&self, item: &U) -> bool
    where
        Idx: [const] PartialOrd<U>,
        U: ?Sized + [const] PartialOrd<Idx>;
}

impl<T> const RangeBounds<T> for RangeToInclusive<T> { /* ... */ }
impl<T> const RangeBounds<T> for RangeToInclusive<&T> { /* ... */ }

impl<T> const From<RangeToInclusive<T>> for legacy::RangeToInclusive<T> { /* ... */ }
impl<T> const From<legacy::RangeToInclusive<T>> for RangeToInclusive<T> { /* ... */ }

unsafe impl<T> const SliceIndex<[T]> for range::RangeToInclusive<usize> {
    type Output = [T];
    /* ... */
}

Tracking issue: #125687

r? @tgross35

[rustbot]

tgross35 is currently at their maximum review capacity.
They may take a while to respond.

[tgross35]

I think there is a small change needed here but otherwise LGTM. However, I noticed there are some trait implementations missing compared to ops::RangeToInclusive:

• OneSidedRange<T>
• RangeBounds<T> for RangeToInclusive<&T> (currently has for RangeToInclusive<T>
• SliceIndex<ByteStr> for RangeToInclusive<usize>
• SliceIndex<str> for RangeToInclusive<usize>

Would you mind putting up a PR adding those? We can re-nominate this for libs-api after.

View changes since this review

[tgross35]

Shouldn't this remain unstable under range_into_bounds?

[rustbot]

Reminder, once the PR becomes ready for a review, use @rustbot ready.

[tgross35]

Index<RangeFrom<usize>> for CStr is also missing in the new RangeFrom