-
Notifications
You must be signed in to change notification settings - Fork 13.9k
Clippy subtree update #147779
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 #147779
Conversation
Volatile reads and writes to non-primitive types are not well-defined, and can cause problems. See rust-lang/rust-clippy#15529 for more details.
switch around `*_amount` and `*_expr` -- otherwise the order gets confusing now because of both of them being `Expr`s
this is kind of a side-effect of the next commit
changelog: none Signed-off-by: Zihan <zihanli0822@gmail.com>
now lints on ```rs let mut x = [1,2,3].into_iter(); loop { let Some(x) = x.next() else { break }; dbg!(x); } ``` ``` changelog: [`while_let_loop`]: extend to lint on `let else` ```
Volatile reads and writes to non-primitive types are not well-defined, and can cause problems. Fixes rust-lang/rust-clippy#15529 changelog: [`volatile_composites`]: Lint when read/write_volatile is used on composite types (structs, arrays, etc) as their semantics are not well defined.
Remove no-rustfixes where it's not required anymore changelog: none
…avidtwco test: Subtract code_offset from width for ui_testing `annotate-snippets` does not have a "UI test" mode like `rustc`, [where the code offset is not subtracted from the column width](https://github.com/rust-lang/rust/blob/f34ba774c78ea32b7c40598b8ad23e75cdac42a6/compiler/rustc_errors/src/emitter.rs#L1985-L1987). This makes it so `annotate-snippets` will shift the output for some very long tests 5 - 7 columns to the left. As part of my work to have `rustc` use `annotate-snippets`, and to reduce the test differences between the two, I figured it would be best if `rustc` started subtracting the code offset from the width as well. The first commit exists to keep the test output changes of adding a new line to a test separate from adding the `--diagnostic-width` flag in the second commit. This makes it easier to verify that adding the flag does not affect the test's output. [Zulip discussion](https://rust-lang.zulipchat.com/#narrow/channel/147480-t-compiler.2Fdiagnostics/topic/annotate-snippets.20hurdles)
changelog:none
…ang#15816) Fixes rust-lang/rust-clippy#15805 ICE bisects to 9457d64, which handles the span incorrectly when part of the path originates from internal declarative macro. changelog: none
…rn suggestions (rust-lang#15608) Fixes rust-lang/rust-clippy#13287 changelog: [`collapsible_match`]: exclude binding modes from struct field pattern suggestions
Adds a new lint that detects `var = Default::default()` when `var` is `Box<T>` and `T` implements `Default`. changelog: [`replace_box`]: new lint
…-lang#15547) Closes rust-lang/rust-clippy#14550 Closes rust-lang/rust-clippy#15548 changelog: [`needless_continue`] fix FP when match type is not unit or never
9895efc
to
4b0cfb6
Compare
The above issue should be fixed now. |
@bors r+ |
Clippy subtree update r? `@Manishearth` `Cargo.lock` update, because `clippy_utils` is now also using `itertools`
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
It looks like the test that made it fail is spuriously failing a lot. @bors retry |
(I've open this Zulip thread on the repeated failure of the mingw test) |
☀️ 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 28c4c7d (parent) -> a41214f (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 a41214f9bd7ce869d21898f31107f92c90a9112f --output-dir test-dashboard And 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 (a41214f): 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 1.2%, secondary 4.3%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (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: 474.3s -> 476.516s (0.47%) |
…nishearth Clippy subtree update r? `@Manishearth` `Cargo.lock` update, because `clippy_utils` is now also using `itertools`
r? @Manishearth
Cargo.lock
update, becauseclippy_utils
is now also usingitertools