Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Why `fiber::mutex` yields in `try_lock` even after acquiring the lock successfully?

Open
#331 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp

Research direction

Read src/mutex.cpp at lines 43-60 and trace the fiber::mutex try_lock path to understand why it yields after attempting the lock. Confirm the intended behavior with the project maintainers; done means either documenting the rationale or agreeing on a change to the return behavior.

Written by the indexing model from the issue text.

Description

Recently I'm reading the source code of fiber::mutex, I noticed thatfiber::mutex will yield in try_lock no matter whether holding the lock or not? What's the considerations behind it, and can we just return immediately after lock? Thanks in advance.
https://github.com/boostorg/fiber/blob/238487b543e8863c647d31a82ccfc3fa11a960d9/src/mutex.cpp#L43-L60

Dominant language
C++
Stars
511
Forks
123
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from boostorg/fiber

All issues in boostorg/fiber

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.