-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
Clippy subtree update #150818
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 #150818
Conversation
changelog: [`transmuting_null`]: now checks single expression const blocks and blocks
This fixes the ICE reported by rejecting `const` blocks in pattern position during AST lowering. Previously, `ExprKind::ConstBlock` could reach HIR as `PatExprKind::ConstBlock`, allowing invalid patterns to be type-checked and triggering an ICE. This patch removes the lowering path for const blocks in patterns and emits a proper diagnostic instead. A new UI test is added to ensure the compiler reports a regular error and to prevent regressions.
rust-lang/rust-clippy#16224 changelog: [`double_parens`]: fix FP on macro repetition patterns
Closes rust-lang/rust-clippy#16293 Also contains fixes of several other lints, on handling macros changelog: [`checked_conversions`] fix wrongly unmangled macros changelog: [`manual_ignore_case_cmp`] fix wrongly unmangled macros changelog: [`manual_ilog2`] fix wrongly unmangled macros changelog: [`needless_bool_assign`] fix wrongly unmangled macros changelog: [`manual_is_multiple_of`] fix wrongly unmangled macros
Fairly simple and self explanatory, the actual config value is `allowed-duplicate-crates` not `allowed_duplicate_crates` and will throw an error if you use the wrong one. changelog: Fix typoed mention of config value using `_` of `-`
…8, r=dianne Fix ICE by rejecting const blocks in patterns during AST lowering (closes rust-lang#148138) This PR fixes the ICE reported in rust-lang#148138. The root cause is that `const` blocks aren’t allowed in pattern position, but the AST lowering logic still attempted to create `PatExprKind::ConstBlock`, allowing invalid HIR to reach type checking and trigger a `span_bug!`. Following the discussion in the issue, this patch removes the `ConstBlock` lowering path from `lower_expr_within_pat`. Any `ExprKind::ConstBlock` inside a pattern is now handled consistently with other invalid pattern expressions. A new UI test is included to ensure the compiler reports a proper error and to prevent regressions. Closes rust-lang#148138.
The original documentation had me confused for a couple of minutes. Now it should be more or less unambiguous. changelog: none
…lang#16084) Closes rust-lang/rust-clippy#14989 changelog: [`redundant_pattern_matching`] fix missing `)` in suggestion span
Extremely small change, -0.018% performance improvement on `tokio` Just some warmup for continuing on larger optimizations (i.e. `nonminimal_bool`) changelog:Remove allocations via String pre-allocating.
This removes another single allocation (namely by writing into an already existing `String` instead of allocating a new one just to `push_str` it). r? @blyxyas --- changelog: none
|
💔 Test for c9f505d failed: CI. Failed jobs:
|
This comment has been minimized.
This comment has been minimized.
Closes rust-lang/rust-clippy#16351 changelog: [`unnecessary_to_owned`] fix wrongly unmangled macros
This comment was marked as outdated.
This comment was marked as outdated.
fc94dfc to
d283798
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment has been minimized.
This comment has been minimized.
|
Darn, the MGCA literals support has been merged in the meantime! |
|
I'm testing https://github.com/samueltardieu/rust/tree/clippy-subtree-update with an updated version of my ConstArgKind commit to accomodate changes made in r-l/rust. |
|
@flip1995 I think you can replace my penultimate commit by the one from https://github.com/samueltardieu/rust/tree/clippy-subtree-update (1dd7896). |
|
Ah thanks, didn't see your message until I fixed it myself. |
|
pr-check-2 is now green @bors r=Manishearth,samueltardieu p=1 rollup=never |
This comment has been minimized.
This comment has been minimized.
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 a3f2d5a (parent) -> 1191620 (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 1191620b8c4a93074796408afa538e086acf38c7 --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 (1191620): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)Results (primary 2.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
CyclesResults (primary 2.0%, secondary 0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Binary sizeResults (secondary -0.1%)A less reliable metric. May be of interest, but not used to determine the overall result above.
Bootstrap: 473.694s -> 472.536s (-0.24%) |
r? Manishearth
Cargo.lock update due to askama bump to be in line with the Rust repo.