# \[Concurrency\] Actors & actor isolation

**URL:** <https://forums.swift.org/t/concurrency-actors-actor-isolation/41613>\
**Category:** Pitches\
**Tags:** concurrency\
**Created:** [October 30, 2020, 5:33pm UTC](https://forums.swift.org/t/concurrency-actors-actor-isolation/41613 "2020-10-30T17:33:02Z")\
**Posts on this page:** 1\
**Showing post:** 66

<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 1, 2020, 5:45pm UTC](https://forums.swift.org/t/concurrency-actors-actor-isolation/41613/66 "2020-11-01T17:45:46Z")

</div>

That example should be reliably optimized because there’s no significant code between two calls with known actor-independence. We may have to impose some high-level rules about when we can reasonably assume actor-independence, or else we’ll find ourselves completely blocked by theoretical actor dependencies like, say, a global function reading from actor-protected state somehow.

---

_[View the full topic](https://forums.swift.org/t/concurrency-actors-actor-isolation/41613)._
