Clippy
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- rust
- Domain
- devtools, testing-qa
Research direction
Start by reading the linked rustd project for context; the issue does not identify files, tests, or a specific implementation entry point. It proposes Clippy support, a watch mode that tracks impacted tests, and streamed test results, so the first step is to narrow this into one concrete behavior with a way to verify it.
Written by the indexing model from the issue text.
Description
Clippy support would be amazing! It's abysmally slow right now for large projects, and could probably benefit from this approach.
I experimented with supporting testing on a branch, and I think it might also be cool to have something like rustd test --watch which is able to continuously detect new tests and hot patch them in, and track code changes that would affect unit tests and only run impacted tests. this would let CI run in repos with 100k+ unit tests in milliseconds, since it would surgically target only the impacted tests.
Also agents wouldn't ever have to run tools to get tests results, it could be streamed from MCP as soon as its a valid build, when the code changes affect tests.
https://github.com/DrewRidley/rustd
Most of it is up here if you want any inspiration. Thanks!
- Dominant language
- Rust
- Stars
- 248
- Forks
- 13
- Avg merge
- 7h 52m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from DioxusLabs/rustd
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
DioxusLabs/rustd#15 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
DioxusLabs/rustd#28 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
DioxusLabs/rustd#27 ·
Maintainers usually reply within 1 day
-
Workspace fails to load: rquickjs types give layout of …: HasErrorType, and rustd never falls backOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
DioxusLabs/rustd#26 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
DioxusLabs/rustd#25 ·
Maintainers usually reply within 1 day
All issues in DioxusLabs/rustd
Similar issues
-
bug rust
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
oxc-project/oxc-htmlish-parser#34 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
longbridge/nsh#2541 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100