thunderbird / thunderbird/operation-queue-rs
Allow multithreading to `OperationQueue` with a feature
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
We currently cannot require a trait bound on Send for queue items because of some compatibility issues with Thunderbird's internal types, but having it would be helpful with runtimes like tokio that make spawning a local task a bit painful (don't refer to the example in the readme, it's a bit incorrect in that regard). We could introduce a send feature that redefines QueuedOperation with such a bound, which would allow the queue to be used more easily with runtimes that are friendlier to use in this kind of context.
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 locating OperationQueue and QueuedOperation, then inspect how the crate defines features and handles Thunderbird compatibility. Review the README example only for context, since the issue notes it is inaccurate. Done means a send feature supports Send-bound queue items for multithreaded runtimes without breaking existing compatibility.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100