Bind to the tokio ecosystem?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 425
- Forks
- 163
- Avg merge
- 10h 51m
- Merged PRs (30d)
- 3
Description
We use several tokio components in the code, which requires the tokio runtime. We should replace them with runtime independent ones, e.g. futures-timer.
If we cannot get rid of it, we can consider fully accept the tokio components instead of using runtime-independent ones.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by inventorying the Tokio components used across the repository and comparing them with the runtime-independent alternatives mentioned; done requires a documented, project-wide decision and consistent dependency usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100