swe-productivity/rust-clippy

AI Summary: The GitHub issue proposes extending the `never_loop` Clippy lint to also check iterator reduction functions, such as `for_each`, when their provided closure always diverges. Currently, the lint only targets explicit loop constructs (`loop`, `while`, `for`). The rationale is that such iterator calls with diverging closures (e.g., `iter.for_each(|x| panic!())`) only execute once, which is likely an unintended bug, similar to a `for` loop that always diverges.

AI Summary: The user requests an enhancement to the `redundant_field_names` lint. Currently, it flags if *any* field name matches its value (e.g., `field: field`). The suggestion is to split or modify the lint to distinguish between cases where *all* fields are redundant versus *some* fields, to avoid inconsistent code styling when only a few fields are redundant.

AI Summary: This GitHub issue proposes a new Clippy lint. The lint should identify instances where users unnecessarily combine `enumerate()`, `find()`, and `.unwrap().0` to get the index of an item (e.g., `iter().enumerate().find(|&(_, &ch)| ch == '|').unwrap().0`). It should suggest replacing this verbose pattern with the more concise and efficient `iter().position(|&ch| ch == '|').unwrap()`, provided the `find` predicate only depends on the item and not its index.