rust-lang / rust-lang/rust

Tracking Issue for `rwlock_try_upgrade`

Open
#138,559 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue E-hard E-help-wanted T-libs
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

Feature gate: #![feature(rwlock_try_upgrade)]

This is a tracking issue RwLock::try_upgrade, which turns a read guard into a write guard if it is the only lock accessor.

Public API
// src/sync/rwlock.rs
impl<'a, T: ?Sized> RwLockReadGuard<'a, T> {
    pub fn try_upgrade(orig: Self) -> Result<RwLockWriteGuard<'a, T>, RwLockReadGuard<'a, T>>;
}
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

Start with src/sync/rwlock.rs and review the ACP and partial implementation linked in the tracking issue. Follow the remaining checklist items, including the Clippy and Miri work, FCP, and stabilization PR; the issue is complete when the feature has passed the stated stabilization process.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.