2016-01-24 10:16:56 +01:00
|
|
|
//! lint when items are used after statements
|
|
|
|
|
2021-03-15 19:55:45 -05:00
|
|
|
use clippy_utils::diagnostics::span_lint;
|
2020-03-01 12:23:33 +09:00
|
|
|
use rustc_ast::ast::{Block, ItemKind, StmtKind};
|
2021-08-07 01:15:29 +02:00
|
|
|
use rustc_lint::{EarlyContext, EarlyLintPass};
|
2020-10-14 23:49:48 -04:00
|
|
|
use rustc_middle::lint::in_external_macro;
|
2020-01-11 20:37:08 +09:00
|
|
|
use rustc_session::{declare_lint_pass, declare_tool_lint};
|
2016-01-24 10:16:56 +01:00
|
|
|
|
2018-03-28 15:24:26 +02:00
|
|
|
declare_clippy_lint! {
|
2021-07-02 20:37:11 +02:00
|
|
|
/// ### What it does
|
|
|
|
/// Checks for items declared after some statement in a block.
|
2019-03-05 11:50:33 -05:00
|
|
|
///
|
2021-07-02 20:37:11 +02:00
|
|
|
/// ### Why is this bad?
|
|
|
|
/// Items live for the entire scope they are declared
|
2019-03-05 11:50:33 -05: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-02 20:37:11 +02:00
|
|
|
/// ### Example
|
2019-03-05 11:50:33 -05:00
|
|
|
/// ```rust
|
2020-05-29 18:15:42 +02:00
|
|
|
/// // Bad
|
2019-03-05 11:50:33 -05:00
|
|
|
/// fn foo() {
|
|
|
|
/// println!("cake");
|
|
|
|
/// }
|
|
|
|
///
|
|
|
|
/// fn main() {
|
|
|
|
/// foo(); // prints "foo"
|
|
|
|
/// fn foo() {
|
|
|
|
/// println!("foo");
|
|
|
|
/// }
|
|
|
|
/// foo(); // prints "foo"
|
|
|
|
/// }
|
|
|
|
/// ```
|
2020-05-29 18:15:42 +02:00
|
|
|
///
|
|
|
|
/// ```rust
|
|
|
|
/// // Good
|
|
|
|
/// fn foo() {
|
|
|
|
/// println!("cake");
|
|
|
|
/// }
|
|
|
|
///
|
|
|
|
/// fn main() {
|
|
|
|
/// fn foo() {
|
|
|
|
/// println!("foo");
|
|
|
|
/// }
|
|
|
|
/// foo(); // prints "foo"
|
|
|
|
/// foo(); // prints "foo"
|
|
|
|
/// }
|
|
|
|
/// ```
|
Added `clippy::version` attribute to all normal lints
So, some context for this, well, more a story. I'm not used to scripting, I've never really scripted anything, even if it's a valuable skill. I just never really needed it. Now, `@flip1995` correctly suggested using a script for this in `rust-clippy#7813`...
And I decided to write a script using nushell because why not? This was a mistake... I spend way more time on this than I would like to admit. It has definitely been more than 4 hours. It shouldn't take that long, but me being new to scripting and nushell just wasn't a good mixture... Anyway, here is the script that creates another script which adds the versions. Fun...
Just execute this on the `gh-pages` branch and the resulting `replacer.sh` in `clippy_lints` and it should all work.
```nu
mv v0.0.212 rust-1.00.0;
mv beta rust-1.57.0;
mv master rust-1.58.0;
let paths = (open ./rust-1.58.0/lints.json | select id id_span | flatten | select id path);
let versions = (
ls | where name =~ "rust-" | select name | format {name}/lints.json |
each { open $it | select id | insert version $it | str substring "5,11" version} |
group-by id | rotate counter-clockwise id version |
update version {get version | first 1} | flatten | select id version);
$paths | each { |row|
let version = ($versions | where id == ($row.id) | format {version})
let idu = ($row.id | str upcase)
$"sed -i '0,/($idu),/{s/pub ($idu),/#[clippy::version = "($version)"]\n pub ($idu),/}' ($row.path)"
} | str collect ";" | str find-replace --all '1.00.0' 'pre 1.29.0' | save "replacer.sh";
```
And this still has some problems, but at this point I just want to be done -.-
2021-10-21 21:06:26 +02:00
|
|
|
#[clippy::version = "pre 1.29.0"]
|
2016-02-06 00:13:29 +01:00
|
|
|
pub ITEMS_AFTER_STATEMENTS,
|
2018-03-28 15:24:26 +02:00
|
|
|
pedantic,
|
2016-08-06 10:18:36 +02:00
|
|
|
"blocks where an item comes after a statement"
|
2016-02-06 00:13:29 +01:00
|
|
|
}
|
2016-01-24 10:16:56 +01:00
|
|
|
|
2019-04-08 13:43:55 -07:00
|
|
|
declare_lint_pass!(ItemsAfterStatements => [ITEMS_AFTER_STATEMENTS]);
|
2016-01-24 10:16:56 +01:00
|
|
|
|
2016-03-19 15:06:56 +01:00
|
|
|
impl EarlyLintPass for ItemsAfterStatements {
|
2018-07-23 13:01:12 +02:00
|
|
|
fn check_block(&mut self, cx: &EarlyContext<'_>, item: &Block) {
|
2021-08-07 01:15:29 +02:00
|
|
|
if in_external_macro(cx.sess, item.span) {
|
2016-01-24 10:16:56 +01:00
|
|
|
return;
|
|
|
|
}
|
2016-06-28 15:54:23 +02:00
|
|
|
|
2020-11-28 17:18:15 +01:00
|
|
|
// skip initial items and trailing semicolons
|
2018-11-27 21:14:15 +01:00
|
|
|
let stmts = item
|
|
|
|
.stmts
|
2017-09-05 11:33:04 +02:00
|
|
|
.iter()
|
2019-09-27 17:16:06 +02:00
|
|
|
.map(|stmt| &stmt.kind)
|
2020-11-28 17:18:15 +01:00
|
|
|
.skip_while(|s| matches!(**s, StmtKind::Item(..) | StmtKind::Empty));
|
2016-06-28 15:54:23 +02:00
|
|
|
|
2016-01-24 10:16:56 +01:00
|
|
|
// lint on all further items
|
|
|
|
for stmt in stmts {
|
2016-06-28 15:54:23 +02:00
|
|
|
if let StmtKind::Item(ref it) = *stmt {
|
2021-08-07 01:15:29 +02:00
|
|
|
if in_external_macro(cx.sess, it.span) {
|
2016-06-28 15:54:23 +02:00
|
|
|
return;
|
2016-01-24 10:16:56 +01:00
|
|
|
}
|
2019-09-27 17:16:06 +02:00
|
|
|
if let ItemKind::MacroDef(..) = it.kind {
|
2017-03-13 11:09:56 +01:00
|
|
|
// do not lint `macro_rules`, but continue processing further statements
|
|
|
|
continue;
|
|
|
|
}
|
2017-08-09 09:30:56 +02:00
|
|
|
span_lint(
|
|
|
|
cx,
|
|
|
|
ITEMS_AFTER_STATEMENTS,
|
|
|
|
it.span,
|
|
|
|
"adding items after statements is confusing, since items exist from the \
|
2017-09-05 11:33:04 +02:00
|
|
|
start of the scope",
|
2017-08-09 09:30:56 +02:00
|
|
|
);
|
2016-01-24 10:16:56 +01:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|