-
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
Clippy subtree update #134788
Clippy subtree update #134788
Conversation
…_formatting_args`
…formatting argument is passed
This is more likely to be intended as an intra-doc link than it is to be intended as a refdef. If a refdef is intended, it does not need to be nested within a list item or quote. ```markdown - [`LONG_INTRA_DOC_LINK`]: this looks like an intra-doc link, but is actually a refdef. The first line will seem to disappear when rendered as HTML. ```
Co-Authored-By: Jason Newcomb <jsnewcomb@pm.me>
Changelog: extended [`precedence`] to lint for bitmasking and bit shifting without parentheses
The compiler uses `BitSet<Local>`, because the number of locals doesn't get that high, so clippy should do likewise.
This updates the documentation after rust-lang#13694. It is not based on that PR chain and can be merged independently, but should be merged after that PR. This is partly pulled from rust-lang#12762, but removing the Josh parts. This includes instructions on how to publish `clippy_utils`. Closes rust-lang/rust-clippy#13556 (yes, this is the final PR 🙂) r? @blyxyas changelog: `clippy_utils` is now published to crates.io
…nishearth Clippy subtree update r? `@Manishearth`
…a different result
Fixes rust-lang/rust-clippy#10780 We correctly no longer give a warning when a closure is passed to a method, where one of the arguments to that method uses the variable which would be shadowed by an argument to that closure. Uses is defined loosely as any expression used in the calling expression mentions the shadowee binding (except for the closure itself): ```rust #![deny(clippy::shadow_unrelated)] let x = Some(1); let y = x.map(|x| x + 1); ``` will now succeed. See linebender/xilem#745 - without this change, all of the `expect(shadow_unrelated)` in the repository are met; with it, none of them are. changelog: [`shadow_unrelated`]: Don't treat closures arguments as unrelated when the calling function uses them
Remove Node::ArrayLenInfer
The new cases are `x.map(f)` and `x.map_err(f)` when `f` is `Into::into` or `From::from` with the same input and output types.
Lints with more than two segments are unrecognized, instead of having the middle segments truncated.
`Ty.kind()` is a method. changelog: none
r? @ghost changelog: none
Some changes occurred in src/tools/clippy cc @rust-lang/clippy |
@bors p=1 This is 2 syncs in 1, as the last sync didn't go through because of conflicts I didn't get to address. |
c26f0d8
to
4d8acfe
Compare
4d8acfe
to
8a7d8ec
Compare
r? @matthiaskrgr bors r+ |
@bors r+ |
☀️ Test successful - checks-actions |
Finished benchmarking commit (19e75f4): 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 -1.0%, secondary -3.2%)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.
CyclesResults (primary 1.6%, secondary 2.9%)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.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 765.011s -> 763.554s (-0.19%) |
…tthiaskrgr Clippy subtree update r? `@Manishearth`
r? @Manishearth