Clippy

Open
#2 2 comments 1 reaction 0 assignees View on GitHub

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

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DioxusLabs/rustd

All issues in DioxusLabs/rustd

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.