-
Notifications
You must be signed in to change notification settings - Fork 14k
Clippy subtree update #148957
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
Clippy subtree update #148957
Conversation
Their meanings, and the way they're handled in `get_attr`, are pretty similar
- Move it and its helper function `parse_attrs` together to the end of the file, because it's surprising to see front-and-center a struct that's only really used in one place (`cognitive_complexity`). - Avoid panic path in `LimitStack::limit` - Replace `assert` with `debug_assert` to avoid panics in release builds
Reduces code repetition
Now we don't touch, and thus don't break, whatever path `Rc`/`Arc` was specified with
Move `unused_enumerate_index.rs` to `methods`.
Fix rust-lang/rust-clippy#14350 Co-authored-by: Timo <30553356+y21@users.noreply.github.com>
…dead Constify trait aliases Allow `const trait Foo = Bar + [const] Baz;` trait alias declarations. Their rules are the same as with super traits of const traits. So `[const] Baz` or `const Baz` is only required for `[const] Foo` or `const Foo` bounds respectively. tracking issue rust-lang#41517 (part of the general trait alias feature gate, but I can split it out into a separate const trait alias feature gate. I just assumed that const traits would stabilize before trait aliases, and we'd want to stabilize trait aliases together with const trait aliases at the same time) r? ``@compiler-errors`` ``@fee1-dead``
|
@bors p=0 Let's only bump priority once PR CI passes. This test is still failing for me locally for whatever reason. |
|
@bors p=1 PR CI passed. |
Clippy subtree update r? `@Manishearth`
Probably some sort of race between #146627 and when it was reverted in #148896? I'm unsure of how exactly Josh subtrees work, but in this PR's current state, I fear that merging this is gonna re-introduce the perf regression for Clippy, so: |
|
☀️ Try build successful - checks-actions |
|
Yeah this apparently changes the version of tikv-jemalloc-sys for everything in the rustc workspace. Why that? |
src/tools/clippy/Cargo.toml
Outdated
| termize = "0.2" | ||
| color-print = "0.3.4" | ||
| anstream = "0.6.18" | ||
| tikv-jemalloc-sys = { version = "0.6.1", optional = true, features = ['override_allocator_on_supported_platforms'] } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably not say 0.6.1. This is what forces the version bump for everything in the repo, and that's really not something we should do in a subtree sync PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I messed up when resolving conflicts. This was it. I left Cargo.toml untouched and reverted the Cargo.lock changes.
Shouldn't have done the sync at 1am...
84af28b to
b006b3d
Compare
|
@bors r=Manishearth |
|
☀️ Test successful - checks-actions |
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 e92ffc3 (parent) -> cc57d9a (this PR) Test differencesShow 2 test diffs2 doctest diffs were found. These are ignored, as they are noisy. Test dashboardRun cargo run --manifest-path src/ci/citool/Cargo.toml -- \
test-dashboard cc57d9a2ab7f665dbf4c36c126188889bb47886a --output-dir test-dashboardAnd then open Job duration changes
How to interpret the job duration changes?Job durations can vary a lot, based on the actual runner instance |
|
Finished benchmarking commit (cc57d9a): comparison URL. Overall result: ❌ regressions - no action needed@rustbot label: -perf-regression Instruction countOur most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.
Max RSS (memory usage)Results (primary 0.4%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.5%, secondary -3.0%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 470.813s -> 473.602s (0.59%) |
…nishearth Clippy subtree update r? `@Manishearth`
r? @Manishearth