TaskGroup: Keeping a Reference to Child Tasks?

[DevAndArtist (Adrian Meister)]

@ktoso

If we had those, then we can form a "non-escapeable ChildTask" what you could inspect or cancel etc.

I had a similar topic at some point and this was the response:

@lukasa

It's sort of hard to follow what you want here, but I can respond to the question of explicit child task cancellation. I can't think of a particular technical reason to forbid that: it just requires API surface and Swift Evolution work.

My naive thinking is that we don't really need to guard the child task escaping through a reference. The task group guarantees that all child tasks will be done when the group itself is finished, so the reference would only return either a value or an error and the explicit cancelation would be a no-op.