Tracking Issue for vec_try_remove
Open
Nobody has claimed this yet.
C-tracking-issue
disposition-merge
finished-final-comment-period
S-waiting-on-review
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(vec_try_remove)]
This is a tracking issue for https://github.com/rust-lang/libs-team/issues/649
Non-panicking version of Vec::remove which returns Option<T>.
Public API
// core::alloc::vec
impl<T> Vec<T> {
pub fn try_remove(&mut self, index: usize) -> Option<T>;
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- Implementation: https://github.com/rust-lang/rust/pull/146293
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- More non panicking methods?
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 by reviewing the vec_try_remove feature gate, the linked implementation PR #146293, and the feature-lifecycle stabilization guidance. The remaining work is the unchecked stabilization PR; confirm the unresolved question about more non-panicking methods before considering the feature ready for stabilization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100