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

<div class="post-metadata">

**Author:** ![anandabits](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/anandabits/32/355_2.png) [@anandabits](https://forums.swift.org/u/anandabits)\
**Post date:** [November 1, 2020, 7:00pm UTC](https://forums.swift.org/t/concurrency-actors-actor-isolation/41613/69 "2020-11-01T19:00:05Z")

</div>

> [@John\_McCall](#):
>
> I think if we were going to allow this sort of actor-generics, it would need to support actor classes as well; can you figure out a way to make that work?

The `Store` in my example is an `actor class` so I don’t understand the question. Can you elaborate?

Another example from my library is:

```swift
final actor class TupleStore2<Store0: GlobalActor, Store1: GlobalActor>: GlobalActor
  where Store0.ActorContext == Store1.ActorContext
{
    typealias ActorContext = Store0.ActorContext
}

```

In my library `TupleStore2` is actually a struct. Ideally a heap allocation could be avoided but I'm not sure how that could be expressed in terms of the current pitch.

---

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