2016-01-24 03:16:56 -06:00
|
|
|
//! lint when items are used after statements
|
|
|
|
|
2023-03-24 10:29:30 -05:00
|
|
|
use clippy_utils::diagnostics::span_lint_hir;
|
|
|
|
use rustc_hir::{Block, ItemKind, StmtKind};
|
|
|
|
use rustc_lint::{LateContext, LateLintPass, LintContext};
|
2020-11-05 07:29:48 -06:00
|
|
|
use rustc_middle::lint::in_external_macro;
|
2020-01-11 05:37:08 -06:00
|
|
|
use rustc_session::{declare_lint_pass, declare_tool_lint};
|
2016-01-24 03:16:56 -06:00
|
|
|
|
2018-03-28 08:24:26 -05:00
|
|
|
declare_clippy_lint! {
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### What it does
|
|
|
|
/// Checks for items declared after some statement in a block.
|
2019-03-05 10:50:33 -06:00
|
|
|
///
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### Why is this bad?
|
|
|
|
/// Items live for the entire scope they are declared
|
2019-03-05 10:50:33 -06:00
|
|
|
/// in. But statements are processed in order. This might cause confusion as
|
|
|
|
/// it's hard to figure out which item is meant in a statement.
|
|
|
|
///
|
2021-07-29 05:16:06 -05:00
|
|
|
/// ### Example
|
2019-03-05 10:50:33 -06:00
|
|
|
/// ```rust
|
|
|
|
/// fn foo() {
|
|
|
|
/// println!("cake");
|
|
|
|
/// }
|
|
|
|
///
|
|
|
|
/// fn main() {
|
|
|
|
/// foo(); // prints "foo"
|
|
|
|
/// fn foo() {
|
|
|
|
/// println!("foo");
|
|
|
|
/// }
|
|
|
|
/// foo(); // prints "foo"
|
|
|
|
/// }
|
|
|
|
/// ```
|
2020-06-09 09:36:01 -05:00
|
|
|
///
|
2022-06-05 14:24:41 -05:00
|
|
|
/// Use instead:
|
2020-06-09 09:36:01 -05:00
|
|
|
/// ```rust
|
|
|
|
/// fn foo() {
|
|
|
|
/// println!("cake");
|
|
|
|
/// }
|
|
|
|
///
|
|
|
|
/// fn main() {
|
|
|
|
/// fn foo() {
|
|
|
|
/// println!("foo");
|
|
|
|
/// }
|
|
|
|
/// foo(); // prints "foo"
|
|
|
|
/// foo(); // prints "foo"
|
|
|
|
/// }
|
|
|
|
/// ```
|
2021-12-06 05:33:31 -06:00
|
|
|
#[clippy::version = "pre 1.29.0"]
|
2016-02-05 17:13:29 -06:00
|
|
|
pub ITEMS_AFTER_STATEMENTS,
|
2018-03-28 08:24:26 -05:00
|
|
|
pedantic,
|
2016-08-06 03:18:36 -05:00
|
|
|
"blocks where an item comes after a statement"
|
2016-02-05 17:13:29 -06:00
|
|
|
}
|
2016-01-24 03:16:56 -06:00
|
|
|
|
2019-04-08 15:43:55 -05:00
|
|
|
declare_lint_pass!(ItemsAfterStatements => [ITEMS_AFTER_STATEMENTS]);
|
2016-01-24 03:16:56 -06:00
|
|
|
|
2023-03-24 10:29:30 -05:00
|
|
|
impl LateLintPass<'_> for ItemsAfterStatements {
|
|
|
|
fn check_block(&mut self, cx: &LateContext<'_>, block: &Block<'_>) {
|
|
|
|
if in_external_macro(cx.sess(), block.span) {
|
2016-01-24 03:16:56 -06:00
|
|
|
return;
|
|
|
|
}
|
2016-06-28 08:54:23 -05:00
|
|
|
|
2023-03-24 10:29:30 -05:00
|
|
|
// skip initial items
|
|
|
|
let stmts = block
|
2018-11-27 14:14:15 -06:00
|
|
|
.stmts
|
2017-09-05 04:33:04 -05:00
|
|
|
.iter()
|
2023-03-24 10:29:30 -05:00
|
|
|
.skip_while(|stmt| matches!(stmt.kind, StmtKind::Item(..)));
|
2016-06-28 08:54:23 -05:00
|
|
|
|
2016-01-24 03:16:56 -06:00
|
|
|
// lint on all further items
|
|
|
|
for stmt in stmts {
|
2023-03-24 10:29:30 -05:00
|
|
|
if let StmtKind::Item(item_id) = stmt.kind {
|
|
|
|
let item = cx.tcx.hir().item(item_id);
|
|
|
|
if in_external_macro(cx.sess(), item.span) || !item.span.eq_ctxt(block.span) {
|
2016-06-28 08:54:23 -05:00
|
|
|
return;
|
2016-01-24 03:16:56 -06:00
|
|
|
}
|
2023-03-24 10:29:30 -05:00
|
|
|
if let ItemKind::Macro(..) = item.kind {
|
2017-03-13 05:09:56 -05:00
|
|
|
// do not lint `macro_rules`, but continue processing further statements
|
|
|
|
continue;
|
|
|
|
}
|
2023-03-24 10:29:30 -05:00
|
|
|
span_lint_hir(
|
2017-08-09 02:30:56 -05:00
|
|
|
cx,
|
|
|
|
ITEMS_AFTER_STATEMENTS,
|
2023-03-24 10:29:30 -05:00
|
|
|
item.hir_id(),
|
|
|
|
item.span,
|
2017-08-09 02:30:56 -05:00
|
|
|
"adding items after statements is confusing, since items exist from the \
|
2017-09-05 04:33:04 -05:00
|
|
|
start of the scope",
|
2017-08-09 02:30:56 -05:00
|
|
|
);
|
2016-01-24 03:16:56 -06:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|