Optimize cargo-vnd compilation time
Open
Nobody has claimed this yet.
performance
- Dominant language
- Rust
- Stars
- 44
- Forks
- 7
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 3
Description
The compilation time of cargo-vnd is very long, probably because it depends on client_sdk and common crates, while only very small portions of them are needed.
The upstream crates should either be refactored into smaller crates, or it should be possible to gate out the unnecessary features.
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 examining cargo-vnd’s dependencies on the client_sdk and common crates and measuring their contribution to compilation time. Compare whether smaller upstream crates or feature gating is feasible; done means cargo-vnd compiles noticeably faster without losing the portions it needs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100