Mirrors/rust-clippy
2
0
Fork 0
mirror of https://github.com/rust-lang/rust-clippy synced 2024-09-21 07:01:54 +00:00
Code Issues Projects Releases Packages Wiki Activity

Expand docs on clippy::todo

Browse source 
https://doc.rust-lang.org/nightly/core/macro.todo.html
describes that `todo!()` is intended for explicitly unfinished
code. Explain this, and mention `unimplemented!()` as an alternative.

Whilst we're here, improve the punctuation on the other lints.
This commit is contained in:
Wilfred Hughes 2023-10-27 10:22:41 -07:00
parent 2f0f4ddcf7
commit 58fe45102d
1 changed files with 9 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
clippy_lints/src/panic_unimplemented.rs
View file

@ -9,7 +9,7 @@ declare_clippy_lint! {
/// Checks for usage of `panic!`.
///
/// ### Why is this bad?
/// `panic!` will stop the execution of the executable
/// `panic!` will stop the execution of the executable.
///
/// ### Example
/// ```no_run
@ -26,7 +26,7 @@ declare_clippy_lint! {
/// Checks for usage of `unimplemented!`.
///
/// ### Why is this bad?
/// This macro should not be present in production code
/// This macro should not be present in production code.
///
/// ### Example
/// ```no_run
@ -43,12 +43,17 @@ declare_clippy_lint! {
/// Checks for usage of `todo!`.
///
/// ### Why is this bad?
/// This macro should not be present in production code
/// The `todo!` macro is often used for unfinished code, and it causes
/// code to panic. It should not be present in production code.
///
/// ### Example
/// ```no_run
/// todo!();
/// ```
/// Finish the implementation, or consider marking it as explicitly unimplemented.
/// ```no_run
/// unimplemented!();
/// ```
#[clippy::version = "1.40.0"]
pub TODO,
restriction,
@ -60,7 +65,7 @@ declare_clippy_lint! {
/// Checks for usage of `unreachable!`.
///
/// ### Why is this bad?
/// This macro can cause code to panic
/// This macro can cause code to panic.
///
/// ### Example
/// ```no_run