std::shared...lock_shared(3)

💖 NAME 💖

std::shared_mutex::try_lock_shared — ok so it's literally std::shared_mutex::try_lock_shared, the shared-mode try-lock bestie of the C++ Standard Library manual (std::shared...lock_shared(3), iykyk) 🫶

---

✨ Synopsis ✨

bool try_lock_shared();  // (since C++17)

So here's the vibe: this function tries to lock the mutex in shared mode, and it returns immediately — no waiting, no blocking, no "hold on let me think about it" energy 💅 On a successful lock acquisition it returns true, otherwise it returns false. Periodt.

Heads up bestie: this function is allowed to fail spuriously and return false even if the mutex is not currently exclusively locked by any other thread 😭 Not me getting rejected for no reason fr fr.

A prior unlock() operation on the same mutex synchronizes-with (as defined in std::memory_order) this operation if it returns true ⭐

🚨 Ok this one matters: the behavior is undefined if the calling thread already owns the mutex in any mode. Any mode. Don't do it. 🙈

---

🎀 Parameters 🎀

(none) — yeah, she takes nothing, she's low maintenance ✨

---

🌸 Return value 🌸

true if the lock was acquired successfully, otherwise false. That's it, that's the whole story 💖

---

🦋 Exceptions 🦋

Throws nothing. Not a single thing. Iconic behavior honestly 👑

---

🍓 Example 🍓

This section is incomplete.

Reason: no example 🙈

---

🌈 See also 🌈

• lock — locks the mutex, blocks if the mutex is not available (public member function)
• try_lock — tries to lock the mutex, returns if the mutex is not available (public member function)
• unlock_shared — unlocks the mutex (shared ownership) (public member function)

---

💜 Category 💜

• Todo no example

---

🧚 She's giving "I tried my best and I'm leaving immediately" energy and honestly? Respect.

Ok that's the whole page bestie, go forth and lock responsibly 💅✨

Source/version + date check: this one's straight from http://cppreference.com, dated 2024.06.10 — the std::shared...lock_shared(3) page, no cap 🫶🎀