Skip to content

Conversation

flip1995
Copy link
Member

@flip1995 flip1995 commented Sep 4, 2025

y21 and others added 30 commits June 21, 2025 15:02
The first statement of the block might have been in a different context
from the expression. Walk up to the right context to get bounds
properly.

Also, switch to `snippet_with_applicability()` since we know that we are
in the right context already.
`option_map_unwrap_or` and `seek_rewind` are not current lints, and
cannot be referenced as having the `msrv` configuration option.
Before this change, the suggestion for
`Option.or(Some(vec![])).unwrap()` expanded the `vec!` macro which broke
the code, both in terms of readability, and because the expansion
references `$crate` which cannot be inlined.
use trait item's HirId when emitting lint at `check_item` level

changelog: [`missing_inline_in_public_items`]: fix trait item lint emission

Signed-off-by: Zihan <zihanli0822@gmail.com>
avoids bounds checks
`None` is the fallback case anyway
`trait_name` can only be _one_ of those at the same time
Alexendoo and others added 8 commits September 2, 2025 14:08
…ang#15540)

changelog: [`ptr_cast_constness`]: avoid suggesting unresolvable method
call

Spell check says "unresolvable" isn't a word. Which repository do I open
a PR against to fix that?

Fixes rust-lang/rust-clippy#11317
…rors

add span to struct pattern rest (..)

Struct pattern rest (`..`) did not retain span information compared to normal fields. This patch adds span information for it.

The motivation of this patch comes from when I implemented this PR for Clippy: rust-lang/rust-clippy#15000 (comment)

It is possible to get the span of the Et cetera in a bit roundabout way, but I thought this would be nicer.
Forgot to do this at the start of the week. Will be back on the 15th.
(That's also the reason why I forgot about the meeting. Sorry for that!)

r? @ghost

changelog: none
r? @ghost

changelog: integer-to-pointer-transmutes are now handled by the upstream
`integer_to_ptr_transmutes` Rust lint and no longer by the
[`useless_transmute`] Clippy lint
@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 Sep 4, 2025
@rustbot
Copy link
Collaborator

rustbot commented Sep 4, 2025

Some changes occurred in src/tools/clippy

cc @rust-lang/clippy

@rustbot
Copy link
Collaborator

rustbot commented Sep 4, 2025

⚠️ Warning ⚠️

@flip1995
Copy link
Member Author

flip1995 commented Sep 4, 2025

The job was not acquired by Runner of type hosted even after multiple attempts
Internal server error. Correlation ID: bbd75497-6a39-4b01-a5e1-9acaa3e75ea9

🤔 Closing and reopening to restart PR CI

@flip1995 flip1995 closed this Sep 4, 2025
@rustbot rustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Sep 4, 2025
@flip1995 flip1995 reopened this Sep 4, 2025
@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Sep 4, 2025
@Manishearth
Copy link
Member

@bors r+ p=1 rollup=never

@bors
Copy link
Collaborator

bors commented Sep 4, 2025

📌 Commit 75b9ee5 has been approved by Manishearth

It is now in the queue for this repository.

@bors bors 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 Sep 4, 2025
@bors
Copy link
Collaborator

bors commented Sep 5, 2025

⌛ Testing commit 75b9ee5 with merge 91edc3e...

@bors
Copy link
Collaborator

bors commented Sep 5, 2025

☀️ Test successful - checks-actions
Approved by: Manishearth
Pushing 91edc3e to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Sep 5, 2025
@bors bors merged commit 91edc3e into rust-lang:master Sep 5, 2025
13 of 14 checks passed
@rustbot rustbot added this to the 1.91.0 milestone Sep 5, 2025
Copy link
Contributor

github-actions bot commented Sep 5, 2025

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 b3cfb8f (parent) -> 91edc3e (this PR)

Test differences

Show 4 test diffs

4 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 91edc3ebccc4daa46c20a93f4709862376da1fdd --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. dist-aarch64-linux: 5813.9s -> 8966.0s (54.2%)
  2. aarch64-apple: 6463.1s -> 4853.3s (-24.9%)
  3. pr-check-1: 1368.3s -> 1705.4s (24.6%)
  4. x86_64-gnu-llvm-19-1: 3314.4s -> 3621.9s (9.3%)
  5. armhf-gnu: 4670.7s -> 5095.2s (9.1%)
  6. x86_64-msvc-ext3: 6203.8s -> 6694.4s (7.9%)
  7. x86_64-gnu-miri: 4814.9s -> 4434.2s (-7.9%)
  8. x86_64-gnu-llvm-20-1: 3586.2s -> 3309.6s (-7.7%)
  9. x86_64-gnu-tools: 3792.3s -> 3521.1s (-7.2%)
  10. dist-i686-msvc: 8019.0s -> 7457.2s (-7.0%)
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
Collaborator

Finished benchmarking commit (91edc3e): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results (secondary -2.4%)

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)
2.3% [2.3%, 2.3%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-3.5% [-4.6%, -2.6%] 4
All ❌✅ (primary) - - 0

Cycles

Results (primary 2.7%, secondary 3.7%)

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

mean range count
Regressions ❌
(primary)
2.7% [2.7%, 2.7%] 1
Regressions ❌
(secondary)
3.7% [3.7%, 3.7%] 1
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
- - 0
All ❌✅ (primary) 2.7% [2.7%, 2.7%] 1

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 467.377s -> 468.177s (0.17%)
Artifact size: 390.50 MiB -> 390.48 MiB (-0.00%)

@flip1995 flip1995 deleted the clippy-subtree-update branch September 6, 2025 10:57
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. S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. T-clippy Relevant to the Clippy team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.