[Amended] SE-0469: Task Naming

Hello, Swift community.

SE-0469: Task Naming was accepted in late March of last year and was implemented in the Swift 6.2 release. It was recently observed that, in a glaring-in-retrospect oversight, SE-0469 did not include a public API to read the name of an arbitrary Task. The authors have suggested amending SE-0469 to include an (immutable) instance name property on Task.

The LSG discussed this idea, and we have decided that this was a sufficiently obvious mistake and ensuing fix that we'd rather not burden the community with a second open evolution review just for this change. SE-0469 is therefore summarily amended to include this API. You can see the details of the change in the evolution pull request. Please feel free to ask questions and provide feedback in this thread. If there are any significant concerns, the LSG will just step back and run a normal open review for the revision.

The LSG considers this use of a more lightweight post-hoc review to be an exceptional case arising from a simple oversight in the original review. We continue to believe in the general value of open review and do not wish to undermine that.

John McCall
Language Steering Group

10 Likes

To answer a question I'm sure some people have, I believe that, unfortunately, it is not possible to back-deploy the new API on platforms with a stable ABI. The runtime support for reading this from a Task handle simply isn't there on older releases. The new API will therefore have a tighter availability constraint than the rest of the task naming API.

4 Likes