RoaringBitmap / RoaringBitmap/roaring-rs
Reorganize project to use cargo workspaces
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 957
- Forks
- 119
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 1
Description
A workspace is a set of packages that share the same Cargo.lock and output directory
Should be neater all around, no need to tun fmt / clippy / tests with multiple invocations in local dev or CI.
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
Start by inspecting the repository's Cargo manifests and CI configuration to identify the packages and repeated fmt, clippy, and test invocations. Define the workspace layout and verify that local development and CI can run those checks through the workspace with one shared Cargo.lock and output directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100