From 46c5a5d234f13dcf4bb4cf4241b2addedbf0be14 Mon Sep 17 00:00:00 2001
From: Philipp Krones <hello@philkrones.com>
Date: Mon, 21 Nov 2022 20:34:47 +0100
Subject: Merge commit 'f4850f7292efa33759b4f7f9b7621268979e9914' into clippyup

---
 src/docs/explicit_write.txt | 18 ------------------
 1 file changed, 18 deletions(-)
 delete mode 100644 src/docs/explicit_write.txt

(limited to 'src/docs/explicit_write.txt')

diff --git a/src/docs/explicit_write.txt b/src/docs/explicit_write.txt
deleted file mode 100644
index eafed5d39e5..00000000000
--- a/src/docs/explicit_write.txt
+++ /dev/null
@@ -1,18 +0,0 @@
-### What it does
-Checks for usage of `write!()` / `writeln()!` which can be
-replaced with `(e)print!()` / `(e)println!()`
-
-### Why is this bad?
-Using `(e)println! is clearer and more concise
-
-### Example
-```
-writeln!(&mut std::io::stderr(), "foo: {:?}", bar).unwrap();
-writeln!(&mut std::io::stdout(), "foo: {:?}", bar).unwrap();
-```
-
-Use instead:
-```
-eprintln!("foo: {:?}", bar);
-println!("foo: {:?}", bar);
-```
\ No newline at end of file
-- 
cgit 1.4.1-3-g733a5