rust-lang / rust-lang/rust

Tracking Issue for `core::cell::{Ref,RefMut}::try_map`

Open
#143,801 5 comments 0 reactions 0 assignees View on GitHub

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.)

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

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.