# std::shared_mutex::unlock

> C++ Atlas: `cppatlas.com/w/cpp/thread/shared_mutex/unlock` | Source: https://en.cppreference.com/w/cpp/thread/shared_mutex/unlock | Domain: Concurrency support | Standards: C++17

The mutex must be locked by the current thread of execution, otherwise, the behavior is undefined.

## Official Specification Summary (cppreference)

```cpp
void unlock(); // (since C++17)
```

Unlocks the mutex.

The mutex must be locked by the current thread of execution, otherwise, the behavior is undefined.

This operation *synchronizes-with* (as defined in `std::memory_order`) any subsequent lock operation that obtains ownership of the same mutex.

### Parameters

(none)

### Return value

(none)

### Exceptions

Throws nothing.

### Notes

`unlock()` is usually not called directly: `std::unique_lock` and `std::lock_guard` are used to manage exclusive locking.

### Example

> Note: This section is incomplete Reason: no example

### See also

- [`lock`](https://en.cppreference.com/w/cpp/thread/shared_mutex/lock): locks the mutex, blocks if the mutex is not available (public member function)
- [`try_lock`](https://en.cppreference.com/w/cpp/thread/shared_mutex/try_lock): tries to lock the mutex, returns if the mutex is not available (public member function)
- [C documentation for `mtx_unlock`](https://en.cppreference.com/w/c/thread/mtx_unlock)

---
Attribution: content from https://en.cppreference.com/w/cpp/thread/shared_mutex/unlock (cppreference.com), licensed under CC-BY-SA 3.0 and GFDL. Modified: converted to markdown, study notes added. Offline snapshot of 9 February 2025.