Skip to content

Conversation

flip1995
Copy link
Member

@flip1995 flip1995 commented Nov 7, 2024

ROMemories and others added 30 commits September 26, 2024 10:07
pulldown-cmark: don't pull getopts dep

Don't pull getopts, as it unused. Noticed in rust-lang#131892

changelog: none
Allow to go through clippy lints page without javascript

Fixes rust-lang#13536.

This is the follow-up of rust-lang/rust-clippy#13269.

This PR makes it possible to expand/collapse lints (individually) without JS. To achieve this result, there are two ways:
1. Use `details` and `summary` tags. Problem with this approach is that the web browser search may open the `details` tags automatically if content matching it is inside. From a previous discussion with `@Alexendoo,` it seems to not be a desired behaviour.
2. Use a little trick where you use a `label` and a checkbox where the checkbox is in fact hidden. Then it's just a matter of CSS.

r? `@Alexendoo`

changelog: Allow to go through clippy lints page without JS
…blyxyas

Stop linting manual_bits in any macro invoke

Closes rust-lang#13563.

changelog: [`manual_bits`] No longer lints in macro-generated code
Before this change, adding a lint was a difficult matter
because it always had some overhead involved. This was
because all lints would run, no matter their default level,
or if the user had #![allow]ed them. This PR changes that
@workingjubilee
Copy link
Member

Need mingw-check to pass:

  error: function `validate_diag` is never used
    --> src/tools/clippy/clippy_utils/src/diagnostics.rs:41:4
     |
  41 | fn validate_diag(diag: &Diag<'_, impl EmissionGuarantee>) {
     |    ^^^^^^^^^^^^^
     |
     = note: `-D dead-code` implied by `-D warnings`
     = help: to override `-D warnings` add `#[allow(dead_code)]`

@flip1995
Copy link
Member Author

flip1995 commented Nov 8, 2024

Looks like we never build Clippy in release mode in the Clippy repo.

Should be good now.

@rust-log-analyzer

This comment has been minimized.

@flip1995 flip1995 force-pushed the clippy-subtree-update branch from 6c87427 to 0aafd65 Compare November 8, 2024 09:50
@workingjubilee
Copy link
Member

@bors r=Manishearth

@bors
Copy link
Collaborator

bors commented Nov 8, 2024

📌 Commit 0aafd65 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-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Nov 8, 2024
@bors
Copy link
Collaborator

bors commented Nov 8, 2024

⌛ Testing commit 0aafd65 with merge 59cec72...

@bors
Copy link
Collaborator

bors commented Nov 8, 2024

☀️ Test successful - checks-actions
Approved by: Manishearth
Pushing 59cec72 to master...

@bors bors added the merged-by-bors This PR was explicitly merged by bors. label Nov 8, 2024
@bors bors merged commit 59cec72 into rust-lang:master Nov 8, 2024
7 checks passed
@rustbot rustbot added this to the 1.84.0 milestone Nov 8, 2024
@rust-timer
Copy link
Collaborator

Finished benchmarking commit (59cec72): comparison URL.

Overall result: ❌ regressions - please read the text below

Our benchmarks found a performance regression caused by this PR.
This might be an actual regression, but it can also be just noise.

Next Steps:

  • If the regression was expected or you think it can be justified,
    please write a comment with sufficient written justification, and add
    @rustbot label: +perf-regression-triaged to it, to mark the regression as triaged.
  • If you think that you know of a way to resolve the regression, try to create
    a new PR with a fix for the regression.
  • If you do not understand the regression or you think that it is just noise,
    you can ask the @rust-lang/wg-compiler-performance working group for help (members of this group
    were already notified of this PR).

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

This is the most reliable metric that we have; it was used to determine the overall result at the top of this comment. However, even this metric can sometimes exhibit noise.

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

Max RSS (memory usage)

Results (secondary -1.4%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
- - 0
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-1.4% [-1.5%, -1.3%] 2
All ❌✅ (primary) - - 0

Cycles

Results (secondary 2.1%)

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

mean range count
Regressions ❌
(primary)
- - 0
Regressions ❌
(secondary)
3.6% [3.3%, 3.9%] 3
Improvements ✅
(primary)
- - 0
Improvements ✅
(secondary)
-2.3% [-2.3%, -2.3%] 1
All ❌✅ (primary) - - 0

Binary size

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

Bootstrap: 780.103s -> 779.98s (-0.02%)
Artifact size: 335.34 MiB -> 335.38 MiB (0.01%)

@rustbot rustbot added the perf-regression Performance regression. label Nov 8, 2024
@lqd
Copy link
Member

lqd commented Nov 8, 2024

This doesn't change the compiler, and nalgebra is being noisy.

image

@rustbot label: +perf-regression-triaged

@rustbot rustbot added the perf-regression-triaged The performance regression has been triaged. label Nov 8, 2024
@flip1995 flip1995 deleted the clippy-subtree-update branch November 9, 2024 14:49
@flip1995
Copy link
Member Author

flip1995 commented Nov 9, 2024

@jdonszelmann this includes the Clippy attribute changes, you wanted.

@jdonszelmann
Copy link
Contributor

Amazing ,thanks so much!

@Mark-Simulacrum Mark-Simulacrum removed perf-regression Performance regression. perf-regression-triaged The performance regression has been triaged. labels Nov 11, 2024
mati865 pushed a commit to mati865/rust that referenced this pull request Nov 12, 2024
…nishearth

Clippy subtree update

r? `@Manishearth`
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.