Skip to content

Tracking Issue for new_range_end_bound #155456

@nik-rev

Description

@nik-rev

Feature gate: #![feature(new_range_end_bound)]

This is a tracking issue for rust-lang/libs-team#653

Public API

Before

// core::range
struct RangeInclusive<T>;
struct Range<T>;

// core::ops
trait RangeBounds<T: ?Sized> {
    fn start_bound(&self) -> Bound<&T>;

    fn end_bound(&self) -> Bound<&T>;
}

After

// core::range
struct RangeInclusive<Start, End = Start>;
struct Range<Start, End = Start>;

// core::ops
trait RangeBounds<Start: ?Sized, End: ?Sized = Start> {
    fn start_bound(&self) -> Bound<&Start>;

    fn end_bound(&self) -> Bound<&End>;
}

Steps / History

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

Unresolved Questions

  • None yet.

Footnotes

  1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-unimplementedStatus: The feature has not been implemented.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions