Tracking Issue for `const_binary_search`
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(const_binary_search)]
This is a tracking issue for constifying the family of binary search functions on slice.
Public API
// core::slice
impl<T> [T] {
pub const fn binary_search(&self, x: &T) -> Result<usize, usize>
where
T: [const] Ord,
pub const fn binary_search_by<'a, F>(&'a self, mut f: F) -> Result<usize, usize>
where
F: [const] FnMut(&'a T) -> Ordering + [const] Destruct,
pub const fn binary_search_by_key<'a, B, F>(&'a self, b: &B, mut f: F) -> Result<usize, usize>
where
F: [const] FnMut(&'a T) -> B + [const] Destruct,
B: [const] Ord + [const] Destruct,
pub const fn partition_point<P>(&self, mut pred: P) -> usize
where
P: [const] FnMut(&T) -> bool + [const] Destruct,
}
Steps / History
- Implementation: #159528
- 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
The tracked APIs are in core::slice; start by reviewing implementation PR #159528 and the listed public signatures. Done means the final comment period completes and a stabilization PR is opened.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100