feat(runqueue): Add espp::RunQueue
component
#397
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.
Description
RunQueue
component for asynchronously running functions in a separate thread without having to allocate separate thread objects and with support for prioritizationMotivation and Context
The RunQueue helps minimize wasted heap when you need to trigger many different functions to run asynchronously and sporadically - preventing you from having to allocate different tasks statically for them, when you are OK with prioritized / best-effort execution of the functions.
How has this been tested?
Build and run the new
runqueue/example
on QtPy ESP32s3Screenshots (if appropriate, e.g. schematic, board, console logs, lab pictures):
Types of changes
Checklist:
Software
.github/workflows/build.yml
file to add my new test to the automated cloud build github action.