Tracking Issue for `core::cell::{Ref,RefMut}::try_map`
Open
Nobody has claimed this yet.
C-tracking-issue
needs-fcp
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(refcell_try_map)]
This is a tracking issue for core::cell::{Ref,RefMut}::try_map
Public API
impl<'b, T> Ref<'b, T> {
pub fn try_map<U: ?Sized, E>(
orig: Ref<'b, T>,
f: impl FnOnce(&T) -> Result<&U, E>,
) -> Result<Ref<'b, U>, (Self, E)> ;
}
impl<'b, T> RefMut<'b, T> {
pub fn try_map<U: ?Sized, E>(
mut orig: RefMut<'b, T>,
f: impl FnOnce(&mut T) -> Result<&mut U, E>,
) -> Result<RefMut<'b, U>, (Self, E)>;
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- Implementation: #118087
- First ACP: https://github.com/rust-lang/libs-team/issues/341 (ignored by t-libs-api for 17 months)
- Second ACP: https://github.com/rust-lang/libs-team/issues/586 (accepted within 10 days, lol)
- Separate error type: #153093
- Expanding to cover more types: TBD
- Final comment period (FCP)^1
- Stabilization PR: #152092
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
Begin with the public API shown in the issue and review the linked implementation, ACPs, separate-error issue, and stabilization PR. Done is the completion of the remaining checklist items, including the final comment period and stabilization; the issue currently lists no unresolved questions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100