`never_loop`: Note why the loop will never loop.

描述

loop {
    do_something();
    // No need to point this out.
    panic!();
}

// Imagine something less obvious.
let x = || Some(panic!());

loop {
    // Why doesn't this loop?
    x().unwrap();
}

贡献者指南

技术栈

rust

领域

developer experience

议题类型

feature

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

1-2 days

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

active

清晰度议题是否清楚说明期望改动、验收标准和下一步。

clear

前置要求

Rustclippy developmentlint implementation

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

45

研究方向

The issue requests a note in the `never loop` lint to explain why a loop never iterates for non obvious cases. Implementation involves detecting control flow patterns that guarantee no iteration, such as after a `panic!` or a function that never returns. The maintainers should review existing lint logic in `clippy lints/src/never loop.rs` and avoid adding notes for obvious cases. The assignee and comments provide additional context for the expected behavior.