# \[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:** 18

<div class="post-metadata">

**Author:** ![wear\_here](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/wear_here/32/13609_2.png) [@wear\_here](https://forums.swift.org/u/wear_here)\
**Post date:** [October 30, 2020, 9:35pm UTC](https://forums.swift.org/t/concurrency-actors-actor-isolation/41613/18 "2020-10-30T21:35:10Z")

</div>

Copying [a discussion](https://forums.swift.org/t/swift-concurrency-roadmap/41611/6) from [the roadmap thread](https://forums.swift.org/t/swift-concurrency-roadmap/41611) per suggestion from @Lantua:

If these accesses are disallowed, from the "First Phase: Basic Actor Isolation" example in the roadmap thread:

```swift
    // error: an actor cannot access another's mutable state
    otherActor.mutableArray += ["not allowed"]

    // error: either reading or writing
    print(other.mutableArray.first)

```

What is the meaning of `mutableArray` being declared `internal`?

I see how this proposal adds an axis beyond access control—`mutableArray` is restricted even beyond what `private` would signify:

> synchronous functions may only be invoked by the specific actor instance itself, and _not even by any other instance of the same actor class_.

(my emphasis)

What I am wondering is if these axes are orthogonal: is it at all meaningful that `mutableArray` is `internal` here? I'm not sure that access control modifiers really matter at all for actor state. Perhaps they would matter if the state was annotated `@actorIndependent`? I wonder if the language or the developer tools might clarify this at all.

---

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