# Shared mutable state, Sendable, and locks

**URL:** <https://forums.swift.org/t/shared-mutable-state-sendable-and-locks/64336>\
**Category:** Discussion\
**Created:** [April 11, 2023, 5:09pm UTC](https://forums.swift.org/t/shared-mutable-state-sendable-and-locks/64336 "2023-04-11T17:09:55Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![taylorswift](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/taylorswift/32/43413_2.png) [@taylorswift](https://forums.swift.org/u/taylorswift)\
**Post date:** [April 12, 2023, 2:46pm UTC](https://forums.swift.org/t/shared-mutable-state-sendable-and-locks/64336/9 "2023-04-12T14:46:12Z")

</div>

> [@lukasa](#):
>
> It might be better for the community to produce a micro-package for the "I just want a lock" situation.

surely there is no need for yet another micropackage, a dependency-less module in the existing repo with the lock implementation would be sufficient, no?

i have grown increasingly annoyed with the amount of version timelines that need to be reconciled to use the various server side libraries. (testable builds matter!) we need to stop hitting the "create new GitHub repository" button every time we build something new.

---

_[View the full topic](https://forums.swift.org/t/shared-mutable-state-sendable-and-locks/64336)._