Clippy `nonminimal_bool` Crater run
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
This is not an issue that needs to be fixed, it was just created for a Crater experiment.
Note that this is the first Clippy Crater run. In this case for evaluating the importance of the clippy::nonminimal_bool lint, because it takes up a huge amount of processing time (~24% of linting time in syn-2.0.71).
cc @Urgau
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
The issue describes a Clippy Crater experiment evaluating the clippy::nonminimal_bool lint and its processing cost, with context in the linked Zulip discussions. Start by reading those discussions and the experiment details; this issue is complete when the Crater run has produced the intended evaluation, rather than when a code change is made.
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
- Needs clarification
- Newbie friendliness
- 10/100