[Concurrency] UnownedJob.priority and TaskPriority gains description #63543
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.
For Custom Executors we should give the executors a chance to know the priority of the Job.
It would be weird to expose a
TaskPriority
onJob
since not all Jobs have to be Tasks. So perhaps this conversion might do the job:UnownedJob.Priority -> TaskPriority?
. Open to opinions before I polish this up completely.Worth discussing is that
.priority
perhaps is not saying enough here? As we also haveBasePriority
for tasks 🤔 Might need some discussion what exactly to expose.We also had an old radar about TaskPriority printing very ugly -- just as the raw value, so this addresses it while working in here with priorities.
Resolves: rdar://103052361 #62430