PLSysSec / PLSysSec/cargo-scan
Performance improvements
Open
Nobody has claimed this yet.
enhancement
roadmap-unplanned
- Dominant language
- Rust
- Stars
- 47
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Performance isn't prohibitive for running on a single crate, so this is fine to revisit later, probably roadmap-v1.
Basically two things that would help would be
- Loading rust-analyzer once for the entire workspace of several crates, rather than one instance per-crate
- Caching results so that we don't have to recompute them for known versions of dependent crates -- This may come for free if we support pulling in a sanctioned existing policy from a database somewhere rather than always generating your own.
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 reviewing cargo-scan's workspace processing and how it invokes rust-analyzer for each crate. Then investigate how dependent-crate results are computed and whether sanctioned existing policies are supported. Done means defining and implementing a workspace-wide rust-analyzer strategy and a reliable cache or policy-reuse path, with performance evidence for multi-crate workspaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100