about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors[bot] <bors[bot]@users.noreply.github.com>2018-11-14 13:24:45 +0000
committerbors[bot] <bors[bot]@users.noreply.github.com>2018-11-14 13:24:45 +0000
commit7e0ddef4e7e1c1d891998c676ad7eda7cf0d9ea8 (patch)
tree0d067aaf1cfee82bda653ce481fd465ac9384242
parent973e70cef78495281c82429512533aa8d4ca2bb4 (diff)
parent93324f1acfc1929b935f9fdfec5a0a319679fca5 (diff)
downloadrust-7e0ddef4e7e1c1d891998c676ad7eda7cf0d9ea8.tar.gz
rust-7e0ddef4e7e1c1d891998c676ad7eda7cf0d9ea8.zip
Merge #3428
3428: Typo "too" -> "foo" in format.rs r=matthiaskrgr a=ama0



Co-authored-by: Anton <ama0@users.noreply.github.com>
-rw-r--r--clippy_lints/src/format.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/clippy_lints/src/format.rs b/clippy_lints/src/format.rs
index 41046a98a34..bd9fa6f80be 100644
--- a/clippy_lints/src/format.rs
+++ b/clippy_lints/src/format.rs
@@ -21,7 +21,7 @@ use crate::rustc_errors::Applicability;
 /// **What it does:** Checks for the use of `format!("string literal with no
 /// argument")` and `format!("{}", foo)` where `foo` is a string.
 ///
-/// **Why is this bad?** There is no point of doing that. `format!("too")` can
+/// **Why is this bad?** There is no point of doing that. `format!("foo")` can
 /// be replaced by `"foo".to_owned()` if you really need a `String`. The even
 /// worse `&format!("foo")` is often encountered in the wild. `format!("{}",
 /// foo)` can be replaced by `foo.clone()` if `foo: String` or `foo.to_owned()`