# Explicitly captured \`isolated\` parameter does not change isolation of \`@Sendable\`/\`sending\` closures

**URL:** <https://forums.swift.org/t/explicitly-captured-isolated-parameter-does-not-change-isolation-of-sendable-sending-closures/79502>\
**Category:** Using Swift\
**Tags:** concurrency, isolated\
**Created:** [April 25, 2025, 7:36am UTC](https://forums.swift.org/t/explicitly-captured-isolated-parameter-does-not-change-isolation-of-sendable-sending-closures/79502 "2025-04-25T07:36:34Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ktoso](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/ktoso/32/44526_2.png) [@ktoso](https://forums.swift.org/u/ktoso)\
**Post date:** [April 25, 2025, 12:36pm UTC](https://forums.swift.org/t/explicitly-captured-isolated-parameter-does-not-change-isolation-of-sendable-sending-closures/79502/3 "2025-04-25T12:36:03Z")

</div>

For what it's worth, the semantics you're asking for may be actually expressible using the new APIs we're adding right now: "immediate tasks", please check the review thread over here: [[Returned for revision] SE-0472: Starting tasks synchronously from caller context - #3 by ktoso](https://forums.swift.org/t/returned-for-revision-se-0472-starting-tasks-synchronously-from-caller-context/79311/3)

Basically, this introduces `group.addImmediateTask {}` which very aggressively start the task on the calling context, regardless of any closing over it or not. The existance of that isolated parameter in the surrounding context will be enough to achieve this.

---

_[View the full topic](https://forums.swift.org/t/explicitly-captured-isolated-parameter-does-not-change-isolation-of-sendable-sending-closures/79502)._