# Sending to TaskGroup child task

**URL:** <https://forums.swift.org/t/sending-to-taskgroup-child-task/76405>\
**Category:** Using Swift\
**Created:** [December 5, 2024, 9:17pm UTC](https://forums.swift.org/t/sending-to-taskgroup-child-task/76405 "2024-12-05T21:17:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![KeithBauerANZ](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/keithbaueranz/32/27897_2.png) [@KeithBauerANZ](https://forums.swift.org/u/KeithBauerANZ)\
**Post date:** [December 6, 2024, 6:12am UTC](https://forums.swift.org/t/sending-to-taskgroup-child-task/76405/2 "2024-12-06T06:12:04Z")

</div>

You might find useful information in [Sending, inout sending, Mutex](https://forums.swift.org/t/sending-inout-sending-mutex/76373) in which I recently asked similar questions and got helpful answers!

I think in this case, it's because the compiler doesn't know how many times the closure passed to `withTaskGroup` will be called — if `withTaskGroup` called it twice, it would alias your NonSendable value.

---

_[View the full topic](https://forums.swift.org/t/sending-to-taskgroup-child-task/76405)._