summaryrefslogtreecommitdiffstats
path: root/src/tools/clippy/src/docs/debug_assert_with_mut_call.txt
diff options
context:
space:
mode:
Diffstat (limited to 'src/tools/clippy/src/docs/debug_assert_with_mut_call.txt')
-rw-r--r--src/tools/clippy/src/docs/debug_assert_with_mut_call.txt18
1 files changed, 0 insertions, 18 deletions
diff --git a/src/tools/clippy/src/docs/debug_assert_with_mut_call.txt b/src/tools/clippy/src/docs/debug_assert_with_mut_call.txt
deleted file mode 100644
index 2c44abe1f..000000000
--- a/src/tools/clippy/src/docs/debug_assert_with_mut_call.txt
+++ /dev/null
@@ -1,18 +0,0 @@
-### What it does
-Checks for function/method calls with a mutable
-parameter in `debug_assert!`, `debug_assert_eq!` and `debug_assert_ne!` macros.
-
-### Why is this bad?
-In release builds `debug_assert!` macros are optimized out by the
-compiler.
-Therefore mutating something in a `debug_assert!` macro results in different behavior
-between a release and debug build.
-
-### Example
-```
-debug_assert_eq!(vec![3].pop(), Some(3));
-
-// or
-
-debug_assert!(takes_a_mut_parameter(&mut x));
-``` \ No newline at end of file