Move Threadpool class to separate module #151
Merged
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.
Move the ThreadPool class to a separate module for organization purposes, and to allow adding functionality to mix async
and non-async parallel compute.
This PR is the first step of incorporating parts of #131, which proposed a model to achieve the larger and longer term goals of:
The XetRuntime class in this PR was the current ThreadPool class with added functions to allow spawning compute task; it was designed to allow all the current uses of tokio async primatives that would be better as compute primitives to be turned seamlessly into compute primitives.