-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Proposal: Task.startSynchronously #2698
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
Conversation
589952b
to
b41bec5
Compare
This should be ready to go! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor editorial changes, but otherwise LGTM. Once you've applied these, I can start the review—thanks!
// SE-NNNN's proposed 'name: String? = nil' would be here | ||
priority: TaskPriority? = nil, | ||
executorPreference taskExecutor: consuming (any TaskExecutor)? = nil, | ||
operation: sending @escaping async throws(Failure) -> Success, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the parameter list was dropped here and in startSynchronouslyDetached
—should these by sending @escaping () async throws(Failure) -> Success
?
Co-authored-by: Tony Allevato <[email protected]>
Applied all the comments and I removed the |
@allevato I think we're good here. You can kick off the review then -- I'm offline this week but I'll keep an eye on the review thread, thank you! |
New Concurrency API that allows to "synchronously start a Task from the calling context", allowing for more detailed control over execution ordering and even access async functions from synchronous contexts.