Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: Run nightly Clippy instead of stable and beta. #162

Merged
merged 1 commit into from
Mar 13, 2024
Merged

Conversation

luukvanderduim
Copy link
Collaborator

Run less, cover more, more up-to-date main.

Newer clippy versions have the previous' versions lints plus some more. No matter which toolchain you run, main will be up to date with all lints until new lintes are added.

Downside:
The added nightly lints may contain bugs.
This is true but so do stable.

Either the:

  • errors are not found by the lint in which case we will only learn of the error when the bug gets fixed.
  • errors are false positives. These patterns are usually quickly found and fixed overnight.

If we are bothered by a particular crate we can always #[allow(clippy::bothersome-lint-in-our-context)]

Run less, cover more, more up-to-date `main`.

Newer clippy versions have the previous' versions lints plus some more.
No matter which toolchain you run, `main` will be up to date with all lints
until new lintes are added.

Downside:
The added nightly lints may contain bugs.
This is true but so do stable.

Either the:
 - errors are not found by the lint
   in which case we will only learn of the error when the bug gets fixed.
 - errors are false positives. These patterns are usually quickly found and
   fixed overnight.
@TTWNO
Copy link
Member

TTWNO commented Mar 13, 2024

Wonderful idea! Let's merge!

@TTWNO TTWNO merged commit c3338f4 into main Mar 13, 2024
10 of 11 checks passed
@TTWNO TTWNO deleted the nightly-clippy branch March 13, 2024 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants