summaryrefslogtreecommitdiffstats
path: root/src/tools/clippy/src/docs/zero_sized_map_values.txt
diff options
context:
space:
mode:
Diffstat (limited to 'src/tools/clippy/src/docs/zero_sized_map_values.txt')
-rw-r--r--src/tools/clippy/src/docs/zero_sized_map_values.txt24
1 files changed, 0 insertions, 24 deletions
diff --git a/src/tools/clippy/src/docs/zero_sized_map_values.txt b/src/tools/clippy/src/docs/zero_sized_map_values.txt
deleted file mode 100644
index 0502bdbf3..000000000
--- a/src/tools/clippy/src/docs/zero_sized_map_values.txt
+++ /dev/null
@@ -1,24 +0,0 @@
-### What it does
-Checks for maps with zero-sized value types anywhere in the code.
-
-### Why is this bad?
-Since there is only a single value for a zero-sized type, a map
-containing zero sized values is effectively a set. Using a set in that case improves
-readability and communicates intent more clearly.
-
-### Known problems
-* A zero-sized type cannot be recovered later if it contains private fields.
-* This lints the signature of public items
-
-### Example
-```
-fn unique_words(text: &str) -> HashMap<&str, ()> {
- todo!();
-}
-```
-Use instead:
-```
-fn unique_words(text: &str) -> HashSet<&str> {
- todo!();
-}
-``` \ No newline at end of file