# Understanding Swift's value type thread safety

**URL:** <https://forums.swift.org/t/understanding-swifts-value-type-thread-safety/41406>\
**Category:** Using Swift\
**Tags:** concurrency\
**Created:** [October 23, 2020, 3:16pm UTC](https://forums.swift.org/t/understanding-swifts-value-type-thread-safety/41406 "2020-10-23T15:16:04Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Jumhyn](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jumhyn/32/3891_2.png) [@Jumhyn](https://forums.swift.org/u/Jumhyn)\
**Post date:** [October 23, 2020, 3:59pm UTC](https://forums.swift.org/t/understanding-swifts-value-type-thread-safety/41406/4 "2020-10-23T15:59:43Z")

</div>

Also, just to directly address the bit of the blog post that you quoted:

> [@rob](#):
>
> > Importantly, you can safely pass copies of values across threads without synchronization.

In the examples you've provided, you're not working with different _copies_ of the values in question—all the threads are attempting to modify the same location in memory concurrently.

---

_[View the full topic](https://forums.swift.org/t/understanding-swifts-value-type-thread-safety/41406)._
