Task "factory" functions, proper implementation?

[SwiftedMind (Dennis Müller)]

This is also something I would love to know, it would make these factories/Task wrappers much more convenient to use, but I've not really seen @_inheritActorContext @_implicitSelfCapture in the wild yet.

I guess one risk is that underscored attributes are not technically stable and it is actively discouraged to use them (though I've seen many repositories use them anyways, like @_spi).

Edit: I found this quote about @_implicitSelfCapture in the review of SE-0304

@Douglas_Gregor

Explicit self is there for a specific purpose: to help identify retain cycles by requiring one to explicitly call out self capture where it's likely to cause retain cycles. We intentionally did not make it required everywhere , and then later we removed explicit self in other unlikely scenarios . When capturing self in a task, you effectively need the task to have an infinite loop for that capture to be the cause of a reference cycle. That fits very well with the direction already set for explicit self.

@Douglas_Gregor

It's an underscored attribute because we know we want this effect for the code running in a task, and that's why it's here in this proposal. It's not unlike the "marker protocol" for Sendable in that we know we want the effect, but we want more time to make it available for general use. We should have the discussion later about "dropping the underscore" from the attribute to make this a general feature that will help explicit self be meaningful, but we shouldn't make task creation worse while waiting for that discussion to happen.

Not sure if there's been more discussion on this.