mirror of
https://github.com/rust-lang/rust-clippy
synced 2024-11-30 16:39:26 +00:00
Add missing lint description headers
This commit is contained in:
parent
91997a4df4
commit
ad5653b296
2 changed files with 2 additions and 1 deletions
|
@ -8,6 +8,7 @@ use rustc_middle::lint::in_external_macro;
|
||||||
use rustc_session::{declare_lint_pass, declare_tool_lint};
|
use rustc_session::{declare_lint_pass, declare_tool_lint};
|
||||||
|
|
||||||
declare_clippy_lint! {
|
declare_clippy_lint! {
|
||||||
|
/// ### What it does
|
||||||
/// Checks for usage of the `#[allow]` attribute and suggests replacing it with
|
/// Checks for usage of the `#[allow]` attribute and suggests replacing it with
|
||||||
/// the `#[expect]` (See [RFC 2383](https://rust-lang.github.io/rfcs/2383-lint-reasons.html))
|
/// the `#[expect]` (See [RFC 2383](https://rust-lang.github.io/rfcs/2383-lint-reasons.html))
|
||||||
///
|
///
|
||||||
|
@ -19,7 +20,6 @@ declare_clippy_lint! {
|
||||||
/// (`#![allow]`) are usually used to enable or disable lints on a global scale.
|
/// (`#![allow]`) are usually used to enable or disable lints on a global scale.
|
||||||
///
|
///
|
||||||
/// ### Why is this bad?
|
/// ### Why is this bad?
|
||||||
///
|
|
||||||
/// `#[expect]` attributes suppress the lint emission, but emit a warning, if
|
/// `#[expect]` attributes suppress the lint emission, but emit a warning, if
|
||||||
/// the expectation is unfulfilled. This can be useful to be notified when the
|
/// the expectation is unfulfilled. This can be useful to be notified when the
|
||||||
/// lint is no longer triggered.
|
/// lint is no longer triggered.
|
||||||
|
|
|
@ -3368,6 +3368,7 @@ declare_clippy_lint! {
|
||||||
}
|
}
|
||||||
|
|
||||||
declare_clippy_lint! {
|
declare_clippy_lint! {
|
||||||
|
/// ### What it does
|
||||||
/// Looks for calls to [`Stdin::read_line`] to read a line from the standard input
|
/// Looks for calls to [`Stdin::read_line`] to read a line from the standard input
|
||||||
/// into a string, then later attempting to parse this string into a type without first trimming it, which will
|
/// into a string, then later attempting to parse this string into a type without first trimming it, which will
|
||||||
/// always fail because the string has a trailing newline in it.
|
/// always fail because the string has a trailing newline in it.
|
||||||
|
|
Loading…
Reference in a new issue