diff options
| author | bors <bors@rust-lang.org> | 2023-11-24 17:15:33 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-11-24 17:15:33 +0000 |
| commit | 6cfbe5707546248487d09fc338598254f352edfc (patch) | |
| tree | 17ea07374502f001281905491daace9676214127 /tests/rustdoc-js-std/full-path-function.js | |
| parent | 3e7a63b8d1b56d4e8a440df81eea649c9d6926d7 (diff) | |
| parent | f9c6335a0f1a2a0fb17a67d0aa72eae63bbd8a3f (diff) | |
| download | rust-6cfbe5707546248487d09fc338598254f352edfc.tar.gz rust-6cfbe5707546248487d09fc338598254f352edfc.zip | |
Auto merge of #11862 - christophbeberweil:7125-single-element-loop-over-range, r=llogiq
suggest alternatives to iterate an array of ranges
works towards #7125
changelog: [`single_element_loop`]: suggest better syntax when iterating over an array of a single range
`@thinkerdreamer` and myself worked on this issue during a workshop by `@llogiq` at the RustLab 2023 conference. It is our first contribution to clippy.
When iterating over an array of only one element, _which is a range_, our change suggests to replace the array with the contained range itself. Additionally, a hint is printed stating that the user probably intended to iterate over the range and not the array. If the single element in the array is not a range, the previous suggestion in the form of `let {pat_snip} = {prefix}{arg_snip};{block_str}`is used.
This change lints the array with the single range directly, so any prefixes or suffixes are covered as well.
Diffstat (limited to 'tests/rustdoc-js-std/full-path-function.js')
0 files changed, 0 insertions, 0 deletions