about summary refs log tree commit diff
diff options
context:
space:
mode:
authorKisaragi <48310258+KisaragiEffective@users.noreply.github.com>2023-04-10 01:31:30 +0900
committerGitHub <noreply@github.com>2023-04-10 01:31:30 +0900
commitba1f19ee3087f6c47a4ba0f06b21361e1d38d90f (patch)
tree2003934d52f7437600e16e90f3c8b038ced9461d
parent5109a8a840bab0db9909a9ea3237987de45b28be (diff)
downloadrust-ba1f19ee3087f6c47a4ba0f06b21361e1d38d90f.tar.gz
rust-ba1f19ee3087f6c47a4ba0f06b21361e1d38d90f.zip
apply code review suggestion
Co-authored-by: llogiq <bogusandre@gmail.com>
-rw-r--r--clippy_lints/src/missing_const_for_fn.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/clippy_lints/src/missing_const_for_fn.rs b/clippy_lints/src/missing_const_for_fn.rs
index 0cde9cb08f8..f1831a30461 100644
--- a/clippy_lints/src/missing_const_for_fn.rs
+++ b/clippy_lints/src/missing_const_for_fn.rs
@@ -41,7 +41,7 @@ declare_clippy_lint! {
     /// can't be const as it calls a non-const function. Making `a` const and running Clippy again,
     /// will suggest to make `b` const, too.
     ///
-    /// If you are marking public function with const, doing opposite will break API compatibility.
+    /// If you are marking a public function with `const`, removing it again will break API compatibility.
     /// ### Example
     /// ```rust
     /// # struct Foo {