Tracking Issue for `range_into_bounds`
Open
Nobody has claimed this yet.
C-tracking-issue
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(range_into_bounds)]
This is a tracking issue for the IntoBounds trait.
Public API
// core::ops
pub trait IntoBounds<T: Sized> {
fn into_bounds(self) -> (Bound<T>, Bound<T>);
}
impl<T> IntoBounds<T> for Range<T>
impl<T> IntoBounds<T> for RangeFrom<T>
impl<T> IntoBounds<T> for RangeFull
impl<T> IntoBounds<T> for RangeInclusive<T>
impl<T> IntoBounds<T> for RangeTo<T>
impl<T> IntoBounds<T> for RangeToInclusive<T>
Steps / History
- ACP: https://github.com/rust-lang/libs-team/issues/538
- Implementation: #136904
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the IntoBounds API in core::ops and review the implementation tracked in #136904, then read the stabilization guidance linked in the issue. The remaining milestones are the final comment period and a stabilization PR; completion requires those steps to be resolved for the feature gate.
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
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100