diff options
| author | Jason Newcomb <jsnewcomb@pm.me> | 2025-07-16 15:37:28 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-16 15:37:28 +0000 |
| commit | 786330e02c37d3e9c351852ffc37b43c3d5e9bbf (patch) | |
| tree | 6b1fddedb704139aa2f369904252f9e0e94935bb /tests/rustdoc-js-std/parser-slice-array.js | |
| parent | 041a0f633d676f5b2136ecd5cd12f05978f9b059 (diff) | |
| parent | 75c330bb7f58d0cc781c054126620b0a396e928a (diff) | |
| download | rust-786330e02c37d3e9c351852ffc37b43c3d5e9bbf.tar.gz rust-786330e02c37d3e9c351852ffc37b43c3d5e9bbf.zip | |
Fix `ptr_arg` suggests changes when it's actually better not to bother (#15105)
No longer suggests `&[i32]` or `&mut [i32]` instead of `&Vec<i32>` or `&mut Vec<i32>` (also: `Path` and `PathBuf`, etc.) for the parameter type when the parameter name starts with an underscore (or, if that does not start with one, then a local `let` binding in the function body, pointing to the same value, does) – (Fixes rust-lang/rust-clippy#13489, fixes rust-lang/rust-clippy#13728) ~changelog: fix false positive: [`ptr_arg`] no longer triggers with underscore binding to `&mut` argument~ changelog: fix false positive: [`ptr_arg`] no longer triggers with underscore binding to `&T` or `&mut T` argument *Edit:* This change has been extended to all references, not just mutable ones. See [discussion below](#issuecomment-3006386877).
Diffstat (limited to 'tests/rustdoc-js-std/parser-slice-array.js')
0 files changed, 0 insertions, 0 deletions