diff options
| author | bors <bors@rust-lang.org> | 2023-11-15 12:11:14 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-11-15 12:11:14 +0000 |
| commit | 3ea5bcf5ee614c32a528389b846c1f6016ef2436 (patch) | |
| tree | 0c94c9c0864812eb86693e5c9bea81faf0a3afd1 /tests/rustdoc-js-std/parser-slice-array.js | |
| parent | 7ad3373bb17507dbee0e67f64955e85d9295f09f (diff) | |
| parent | b3073c536b349e6c80e24d8e85182d6d990c4c50 (diff) | |
| download | rust-3ea5bcf5ee614c32a528389b846c1f6016ef2436.tar.gz rust-3ea5bcf5ee614c32a528389b846c1f6016ef2436.zip | |
Auto merge of #11809 - hrxi:pr_if_same_then_else_style, r=Alexendoo
Change `if_same_then_else` to be a `style` lint CC #3770 From https://github.com/rust-lang/rust-clippy/issues/3770#issuecomment-687565594 (`@flip1995):` > Oh I thought I replied to this: I definitely see now that having this > as a correctness lint might be the wrong categorization. What we might > want to do is to just allow this lint, if there are comments in the > arm bodies. But a good first step would be to downgrade this lint to > style or complexity. I would vote for style since merging two arms is > not always less complex. changelog: [`if_same_then_else`]: Change to be a `style` lint
Diffstat (limited to 'tests/rustdoc-js-std/parser-slice-array.js')
0 files changed, 0 insertions, 0 deletions