-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Task executor preference #2187
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
Task executor preference #2187
Conversation
5bdfc48
to
1bef6aa
Compare
The `TaskExecutor` is defined as: | ||
|
||
```swift | ||
public protocol TaskExecutor: Executor { |
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 we should provide some docs here on what is allowed. A TaskExecutor
is allowed to be a pool of threads or a single thread. Both of them are fine and we should call it out on the docs.
Fixed a little typo
I believe this is ready for review now -- the forums thread on pitch also has calmed down, and implementation is almost complete -- only cleanups remain |
Co-authored-by: Doug Gregor <[email protected]>
Co-authored-by: John McCall <[email protected]>
Polishing up details here.
Has some inter-play with both typed-throws and #2174 which are not included here but it attempts to be stand-alone.