# Should we document the behavior of \`Mutex.withLockIfAvailable()\`?

**URL:** <https://forums.swift.org/t/should-we-document-the-behavior-of-mutex-withlockifavailable/83166>\
**Category:** Standard Library\
**Tags:** concurrency, documentation, mutex, synchronization\
**Created:** [November 12, 2025, 3:03pm UTC](https://forums.swift.org/t/should-we-document-the-behavior-of-mutex-withlockifavailable/83166 "2025-11-12T15:03:28Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![John\_McCall](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/john_mccall/32/1351_2.png) [@John\_McCall](https://forums.swift.org/u/John_McCall)\
**Post date:** [November 12, 2025, 11:22pm UTC](https://forums.swift.org/t/should-we-document-the-behavior-of-mutex-withlockifavailable/83166/4 "2025-11-12T23:22:31Z")

</div>

So, how would this stronger guarantee change how you program against this?

---

_[View the full topic](https://forums.swift.org/t/should-we-document-the-behavior-of-mutex-withlockifavailable/83166)._