# Behavior of @ \_inheritActorContext in Global vs Instance Actors

**URL:** <https://forums.swift.org/t/behavior-of-inheritactorcontext-in-global-vs-instance-actors/90196>\
**Category:** Using Swift\
**Tags:** concurrency\
**Created:** [October 22, 2026, 3:13am UTC](https://forums.swift.org/t/behavior-of-inheritactorcontext-in-global-vs-instance-actors/90196 "2026-10-22T03:13:02Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![mattie](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mattie/32/13267_2.png) [@mattie](https://forums.swift.org/u/mattie)\
**Post date:** [October 26, 2026, 9:05pm UTC](https://forums.swift.org/t/behavior-of-inheritactorcontext-in-global-vs-instance-actors/90196/8 "2026-10-26T21:05:54Z")

</div>

I would certainly _take_ just a fix for `Task` has gotten some traction in the past.

> [@Closure isolation control](https://forums.swift.org/t/closure-isolation-control/70378):
>
> Greetings Swift evolvers. For your consideration, I have drafted a proposal allowing for more explicit control over the isolation of closures. You can read the proposal at [nnnn-closure-isolation.md](https://github.com/sophiapoirier/swift-evolution/blob/closure-isolation/proposals/nnnn-closure-isolation-control.md) Please share thoughts and feedback here or as comments on the [pull request](https://github.com/apple/swift-evolution/pull/2322). Thank you.

But I really would like to take a closure look at closure behavior more generally, which I don't _think_ can be fixed by a parameter attribute alone. But I've not actually explored changes of that exact nature closely, and I do not know how feasible they would be. And even if they are, you are 100% right that it would be source-breaking, kinda similar to `NonisolatedNonsendingByDefault`.

---

_[View the full topic](https://forums.swift.org/t/behavior-of-inheritactorcontext-in-global-vs-instance-actors/90196)._