You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
👋
I would like to request an experiment to know if this is a bug in more lints and need disabling.
Beta releases in 13 days as stable and I think the window for backports is passed (?) at least the usual clippy sync, so it would be very helpfull to have this data (I think, not quite sure what is the process exactly).
Concretely, I think the following experiment (which I pieced together from the docs) would be what I would like.
I am not sure about +rustflags vs +cargoflags since those are not super well documented or at least their interaction is a bit unclear.
@craterbot run start=beta end=4b88e00b78888b3c0ce9cae1b10376b3ddfedb6b mode=clippy crates=top-10000 +rustflags=-Znext-solver=coherence
The issue with clippys lintcheck infra is mostly that it was never meant for more than a quick spotcheck, so is incredibly slow, at least on my laptop.
Also the way to triage them is incredibly labor intensive for lintcheck, so not really feasible.
The signal that I am searching for is if there are more crates that
stack overflow on this PRs commit
already did so on beta stack overflow
Then there would need to be no backport on more lints.
IF interested why moving needless_borrows_for_generic_args to nursery
The issue with clippy seems to be a bit of an weird interaction with const-traits (f.ex. Drop on Vec) messing with some of our lints that were not build for this, but it is hard to narrow down. needless_borrows_for_generic_args for example is this code that triggers it:
Small set: @craterbot run mode=clippy crates=top-10000 start=beta end="4b88e00b78888b3c0ce9cae1b10376b3ddfedb6b+rustflags=-Znext-solver=coherence Dclippy::needless_borrows_for_generic_args" p=5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
👋
I would like to request an experiment to know if this is a bug in more lints and need disabling.
Beta releases in 13 days as stable and I think the window for backports is passed (?) at least the usual clippy sync, so it would be very helpfull to have this data (I think, not quite sure what is the process exactly).
Concretely, I think the following experiment (which I pieced together from the docs) would be what I would like.
I am not sure about
+rustflagsvs+cargoflagssince those are not super well documented or at least their interaction is a bit unclear.The issue with clippys
lintcheckinfra is mostly that it was never meant for more than a quick spotcheck, so is incredibly slow, at least on my laptop.Also the way to triage them is incredibly labor intensive for
lintcheck, so not really feasible.The signal that I am searching for is if there are more crates that
betastack overflowThen there would need to be no backport on more lints.
IF interested why moving
needless_borrows_for_generic_argstonurseryThe issue with clippy seems to be a bit of an weird interaction with const-traits (f.ex.
DroponVec) messing with some of our lints that were not build for this, but it is hard to narrow down.needless_borrows_for_generic_argsfor example is this code that triggers it: