liftedinit / liftedinit/many-rs
Cargo timing reports
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 6
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Rust 1.60 added support for collecting information on build, and generate nice reports such as https://blog.rust-lang.org/images/2022-04-07-timing.html
See https://blog.rust-lang.org/2022/04/07/Rust-1.60.0.html#cargo---timings for details about this new feature.
Would be a nice-to-have in the CI
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 Rust 1.60 Cargo timing documentation and the repository's CI configuration to determine where a timing report could be collected. Define what the CI output should contain and where the generated report should be published, then verify the result in a CI run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100