rust-lang / rust-lang/rust

Tracking Issue for `new_range_end_bound`

Open
#155,456 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Feature gate: #![feature(new_range_end_bound)]

This is a tracking issue for https://github.com/rust-lang/libs-team/issues/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.

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

Start with the public API section and the linked ACP and implementation PR for the new_range_end_bound feature. Follow the listed lifecycle steps; completion requires the implementation, final comment period, and stabilization PR to be addressed.

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
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.