-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Update Clippy #105827
Update Clippy #105827
Conversation
Lower them into a single item with multiple resolutions instead. This also allows to remove additional `NodId`s and `DefId`s related to those additional items.
Don't lint `string_lit_as_bytes` in match scrutinees fixes rust-lang#9885 changelog: `string_lit_as_bytes`: Don't lint in match scrutinees
…=xFrednet Fix manual_let_else produces a wrong suggestion with or-patterns Fix rust-lang#9938 changelog: Sugg: [`manual_let_else`]: Suggestions for or-patterns now include required brackets. [rust-lang#9966](rust-lang/rust-clippy#9966)
Don't suggest removing `mut` from references in `redundant_static_lifetimes` fixes rust-lang#9890 changelog: `redundant_static_lifetimes`: Don't suggest removing `mut` from references
Treat custom enum discriminant values as constants fixes rust-lang#9882 changelog: All lints: Don't lint in enum discriminant values when the suggestion won't work in a const context
…s, r=lcnr `SimplifiedType` cleanups r? `@lcnr`
Fix new_return_no_self with recursive bounds Fix rust-lang#10041 This uses a hash set, as described in rust-lang/rust-clippy#10068 (comment) changelog: [`new_return_no_self`]: fix stack overflow when the return type is `impl Trait` and contains recursive bounds
There used to be a logical bug where IncrementVisitor would completely stop checking an expression/block after seeing a continue statement. This led to issue rust-lang#10058 where a variable incremented (or otherwise modified) after any continue statement would still be considered incremented only once. The solution is to continue scanning the expression after seeing a `continue` statement, but increment self.depth so that the Visitor thinks that the rest of the loop is within a conditional.
…Frednet fix logic in IncrementVisitor There used to be a logical bug where IncrementVisitor would completely stop checking an expression/block after seeing a continue statement. I am a little unsure of whether my fix to `IncrementVisitor` is logically sound (I hope it makes sense). Let me know what you think, and thanks in advance for the review! fixes rust-lang#10058 --- changelog: FP: [`explicit_counter_loop`]: No longer ignores counter changes after `continue` expressions [rust-lang#10094](rust-lang/rust-clippy#10094) <!-- changelog_checked -->
fix: not suggest seek_to_start_instead_of_rewind when expr is used changelog: [`seek_to_start_instead_of_rewind`]: No longer lints, if the return of `seek` is used. [rust-lang#10096](rust-lang/rust-clippy#10096) <!-- changelog_checked --> Fixes rust-lang#10065
Rustup r? `@ghost` I'm on the train and my internet is too bad to download the necessary toolchain, so I have to use CI to find sync fallout. changelog: none <!-- changelog_checked -->
Some changes occurred in src/tools/clippy cc @rust-lang/clippy |
@bors r+ p=1 subtree sync |
☀️ Test successful - checks-actions |
Finished benchmarking commit (2d76a9d): comparison URL. Overall result: ✅ improvements - no action needed@rustbot label: -perf-regression Instruction countThis is a highly reliable metric that was used to determine the overall result at the top of this comment.
Max RSS (memory usage)ResultsThis 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.
CyclesThis benchmark run did not return any relevant results for this metric. |
r? @Manishearth