# \`nonisolated lazy let\` on an actor

**URL:** <https://forums.swift.org/t/nonisolated-lazy-let-on-an-actor/63077>\
**Category:** Discussion\
**Created:** [February 11, 2023, 12:36pm UTC](https://forums.swift.org/t/nonisolated-lazy-let-on-an-actor/63077 "2023-02-11T12:36:43Z")\
**Posts on this page:** 1\
**Showing post:** 13

<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:** [February 14, 2023, 4:52pm UTC](https://forums.swift.org/t/nonisolated-lazy-let-on-an-actor/63077/13 "2023-02-14T16:52:39Z")

</div>

Custom actor executors will add an interesting twist to this. It's an immediate consequence of the feature that actors will be able to share a serial executor, which as far as the dynamic runtime is concerned means they share isolation. However, as long as the compiler doesn't understand that relationship statically, it will continue to enforce isolation between them, and you'll even have to `await` when calling between them (but it won't ever dynamically suspend). So whether or not two actors share a serial executor will not affect source and should just have performance implications. If we then add a way to make actor instances _statically_ share isolation, that would allow `await`s to be dropped, `Sendable` checks to be avoided, etc., basically making them the same isolation domain in all phases. But that's not an immediate consequence of adding custom actor executors.

---

_[View the full topic](https://forums.swift.org/t/nonisolated-lazy-let-on-an-actor/63077)._
