[Concurrency] Task namespace, priority and always throwing Task.Handle.get #34475
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
rdar://70141994
This is a follow up after discussions on these pieces of the API;
Each commit should be self explanatory what the change is; the primary one being:
Task
after all is only a namespace; we never get "a task" object in user land; all interaction with "my task" is via async context sensitive static functionsCancellationError
to be thrown, even if a referred to task is not throwing.Follow up to: #34391