summaryrefslogtreecommitdiffstats
path: root/src/tools/clippy/src/docs/suspicious_unary_op_formatting.txt
diff options
context:
space:
mode:
Diffstat (limited to 'src/tools/clippy/src/docs/suspicious_unary_op_formatting.txt')
-rw-r--r--src/tools/clippy/src/docs/suspicious_unary_op_formatting.txt18
1 files changed, 0 insertions, 18 deletions
diff --git a/src/tools/clippy/src/docs/suspicious_unary_op_formatting.txt b/src/tools/clippy/src/docs/suspicious_unary_op_formatting.txt
deleted file mode 100644
index 06fb09db7..000000000
--- a/src/tools/clippy/src/docs/suspicious_unary_op_formatting.txt
+++ /dev/null
@@ -1,18 +0,0 @@
-### What it does
-Checks the formatting of a unary operator on the right hand side
-of a binary operator. It lints if there is no space between the binary and unary operators,
-but there is a space between the unary and its operand.
-
-### Why is this bad?
-This is either a typo in the binary operator or confusing.
-
-### Example
-```
-// &&! looks like a different operator
-if foo &&! bar {}
-```
-
-Use instead:
-```
-if foo && !bar {}
-``` \ No newline at end of file