Skip to content

[6.2][Concurrency] Update task name APIs, move to modifying AEIC funcs#81132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base:release/6.2
Choose a base branch
from

Conversation

ktoso
Copy link
Contributor

@ktosoktoso commented Apr 28, 2025

Description: This adds "task name" parameter to all task creating functions.

This is done in a few ways, e.g. we can backdeploy this to 5.1 in APIs which do not accept the TaskExecutor but it they do we provide a version for 6.0+ etc. This was requested in the SE acceptable of this proposal Acceptance post SE-0469.

This moves all these declarations to gyb since going through them one by one has become unmaintainable otherwise.

Scope/Impact: All task creation APIs now gain a new task name parameter.
Risk: Medium, changes existing APIs rather than adding "even more overloads" though this risk was discussed in the team and accepted. This has a potential to be source breaking it someone used Task.init and friends as function.
Testing: CI testing, source compatibility suite testing
Reviewed by:

Original PR:

Radar:

kubamracekand others added 3 commits April 28, 2025 16:08
…EIC funcs [Concurrency] Lower availability for task names + addTask WIP on changing the always emit into client funcs
…utor [Concurrency] Adjust tests for renamed initializer [Embedded][Concurrency] Workaround for Gyb+concurrency module+embedded Add Task+init gyb to embedded; Remove TaskGroup+Embedded.swift workaround [Concurrency] Undo build workaround
@ktosoktoso requested a review from a team as a code ownerApril 28, 2025 07:15
@ktoso
Copy link
ContributorAuthor

@swift-ci please test

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
@ktoso@kubamracek
close