Ordered single-threaded executor
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 805
- Forks
- 564
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 27
Description
Suggestion from @adolfo-rt:
Currently the ordering of tasks in the single-threaded executor is not exposed to the user. It should be possible to implement a single-threaded executor in which task execution ordering can be specified by the user. This is to further decouple the component topology from its thread execution.
Not a high priority for the current milestone (ROSCon demos) but an eventual goal.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the single-threaded executor and how it currently orders task execution. The issue names no files or tests, so first determine the relevant executor entry points and how ordering could be specified by users. Done means exposing user-defined task ordering while further decoupling component topology from thread execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100