std::shared_lock::release(3)

💅 std::shared_lock::release(3) 💅

okay so this is from the C++ Standard Libary (yes, “Libary” is spelled like that up top, and we are respectfully keeping the typo 💀), and it’s all about std::shared_lock::release. It’s giving “break the association, not the lock” energy. 🦋

🌸 NAME 🌸

std::shared_lock::release — literally std::shared_lock::release, bestie. That’s the name. No cap. ✨

✨ Synopsis ✨

mutex_type* release() noexcept;  (since C++14)

Breaks the association of the associated mutex, if any, and *this.

No locks are unlocked. 🚨 If *this held ownership of the associated mutex prior to the call, the caller is now responsible to unlock the mutex.

⚠️ read that again, bestie: this does not unlock anything. If you had ownership before, you own the unlocking job now. Periodt. 💅

🫶 Parameters 🫶

(none) — no parameters, zero, zilch, not a single argument. Slay. 💖

🎀 Return value 🎀

Pointer to the associated mutex or a null pointer if there was no associated mutex. That’s the whole return-value tea. ⭐

😭 Example 😭

This section is incomplete Reason: no example

yeah bestie, there is literally no example here. 📭 not me hoping for a little demo… 🙈

👀 See also 👀

• unlock — unlocks the associated mutex (public member function).
• disassociates the associated mutex without unlocking (i.e., releasing release ownership of) it (public member function of std::unique_lock<Mutex>).

🗂️ Category 🗂️

• Todo no example

💖 source: http://cppreference.com · date: 2024.06.10 · page: std::shared_lock::release(3) 💖