Skip to content

Clippy subtree update - #159030

Merged
rust-bors[bot] merged 139 commits into
rust-lang:mainfrom
flip1995:clippy-subtree-update
Jul 10, 2026
Merged

Clippy subtree update#159030
rust-bors[bot] merged 139 commits into
rust-lang:mainfrom
flip1995:clippy-subtree-update

Conversation

@flip1995

@flip1995 flip1995 commented Jul 9, 2026

Copy link
Copy Markdown
Member

r? Manishearth

Cargo.lock update due to Clippy version bump and itertools version bump in Clippy.

Jarcho and others added 30 commits March 23, 2026 10:38
i.e. rename:
- filter_map_next -> filter_map_next_unfixable
- filter_map_next_fixable -> filter_map_next

This is because having fixable lints is the common case
separate commit to improve diffs
1. In the singe-line case, we switch to verbose suggestions, otherwise
   the suggestion line gets too long due to the longer message.
2. In the multi-line case, we use span-less help, otherwise the whole
   multiline span gets highlighted the second time.
3. Also make the suggestion message more concise.
It's a bad name: long, and contains a negative. `skippable_lints` is
better.
This used to be a workaround for a rustc diagnostics issue which has
since been resolved
…per, r=GuillaumeGomez

Update `rustc-literal-escaper` version to `0.0.8`

This new version contains a minor performance improvement. More detail in the PR: rust-lang/literal-escaper#27

cc @hkBst
r? ghost
Without this change, `single_range_in_vec_init`, and all lints depending
on `higher::Range`, will not lint range expressions that use the new
`Copy + !Iterator` range types, which occur when `feature(new_range)` is
enabled and will occur when using the future edition where that type
change is the default, stable behavior.

Prior to <rust-lang/rust-clippy#17146>,
`single_range_in_vec_init` did detect such ranges (because it looked for
the desugaring and not what lang item was involved); therefore, this is
also fixing a regression.

Note that because the new range types do not implement `Iterator`, the
`collect()` suggestion must change. I chose `Vec::from_iter(range)` over
`(range).into_iter().collect()` because I believe it is the more elegant
(and intended) solution.
…, r=Urgau

Rework lint pass running



Some cleanups relating to the running of lint passes.

r? @Urgau
@rustbot

rustbot commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

clippy is developed in its own repository. If possible, consider making this change to rust-lang/rust-clippy instead.

cc @rust-lang/clippy

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-clippy Relevant to the Clippy team. labels Jul 9, 2026
@rustbot

rustbot commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

⚠️ Warning ⚠️

@samueltardieu

Copy link
Copy Markdown
Member

@bors r+ rollup=never p=1 (subtree update)

@rust-bors

rust-bors Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

📌 Commit ea05c08 has been approved by samueltardieu

It is now in the queue for this repository.

@rust-bors rust-bors Bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 10, 2026
@rust-bors

This comment has been minimized.

@rust-bors rust-bors Bot added merged-by-bors This PR was explicitly merged by bors. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Jul 10, 2026
@rust-bors

rust-bors Bot commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

☀️ Test successful - CI
Approved by: samueltardieu
Duration: 3h 22m 56s
Pushing ae705ae to main...

@rust-bors
rust-bors Bot merged commit ae705ae into rust-lang:main Jul 10, 2026
14 checks passed
@rustbot rustbot added this to the 1.99.0 milestone Jul 10, 2026
@github-actions

Copy link
Copy Markdown
Contributor
What is this? This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing 31e4b84 (parent) -> ae705ae (this PR)

Test differences

Show 2 test diffs

2 doctest diffs were found. These are ignored, as they are noisy.

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard ae705ae862c518e4e1f8ead45777e18cf4b6a271 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

  1. i686-msvc-1: 3h 5m -> 1h 39m (-46.2%)
  2. arm-android: 1h 8m -> 1h 38m (+44.7%)
  3. x86_64-gnu-debug: 1h 29m -> 2h 2m (+35.8%)
  4. optional-x86_64-gnu-parallel-frontend: 1h 24m -> 1h 50m (+31.2%)
  5. x86_64-gnu-llvm-21-3: 1h 59m -> 1h 24m (-29.2%)
  6. x86_64-mingw-1: 2h 21m -> 2h 58m (+26.0%)
  7. x86_64-gnu-llvm-22-2: 2h 6m -> 1h 34m (-25.3%)
  8. dist-x86_64-musl: 1h 47m -> 2h 12m (+24.2%)
  9. dist-sparcv9-solaris: 1h 34m -> 1h 13m (-22.6%)
  10. dist-arm-linux-musl: 1h 38m -> 1h 16m (-22.4%)
How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

@rust-timer

Copy link
Copy Markdown
Collaborator

Finished benchmarking commit (ae705ae): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-0.1% [-0.3%, -0.0%] 9
All ❌✅ (primary) - - 0

Max RSS (memory usage)

Results (primary -2.0%, secondary -2.3%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
1.6% [1.6%, 1.6%] 1
Improvements ✅
(primary)
-2.0% [-2.0%, -2.0%] 1
Improvements ✅
(secondary)
-6.2% [-6.2%, -6.2%] 1
All ❌✅ (primary) -2.0% [-2.0%, -2.0%] 1

Cycles

Results (primary -3.0%, secondary -1.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
3.4% [2.8%, 4.3%] 4
Improvements ✅
(primary)
-3.0% [-3.0%, -3.0%] 1
Improvements ✅
(secondary)
-3.7% [-9.2%, -1.2%] 7
All ❌✅ (primary) -3.0% [-3.0%, -3.0%] 1

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: 488.684s -> 491.745s (0.63%)
Artifact size: 389.90 MiB -> 389.36 MiB (-0.14%)

@panstromek

Copy link
Copy Markdown
Contributor

Cargo.lock update due to Clippy version bump and itertools version bump in Clippy.

Do I understand correctly that this should not impact compiler dependencies in any way? Or are itertools shared between the two?

rust-bors Bot pushed a commit that referenced this pull request Aug 3, 2026
Clippy subtree update

r? Manishearth

Cargo.lock update due to Clippy version bump and itertools version bump in Clippy.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merged-by-bors This PR was explicitly merged by bors. T-clippy Relevant to the Clippy team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.