Skip to content

Commit 54e929b

Browse files
committed
Auto merge of #10237 - cstyles:fix-docs-for-suspicious_xor_used_as_pow, r=Jarcho
Fix styling in documentation for `suspicious_xor_used_as_pow` lint There was a tab after the three leading slashes which caused the contents of the "Why is this bad?" section to be rendered as a code block. **Before:** <img width="626" alt="master" src="https://user-images.githubusercontent.com/4869194/214985546-4433d211-9fd3-450c-8ff7-2c0a47fccdc0.png"> **After:** <img width="520" alt="fixed" src="https://user-images.githubusercontent.com/4869194/214985561-87255196-008c-4a1c-8cc8-c54b337d22a2.png"> The file still contains a lot of tabs but they don't affect the documentation. --- changelog: [`suspicious_xor_used_as_pow`]: Fix styling in documentation
2 parents b5e3e60 + a1a01c1 commit 54e929b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

clippy_lints/src/suspicious_xor_used_as_pow.rs

+1-1
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ declare_clippy_lint! {
99
/// ### What it does
1010
/// Warns for a Bitwise XOR (`^`) operator being probably confused as a powering. It will not trigger if any of the numbers are not in decimal.
1111
/// ### Why is this bad?
12-
/// It's most probably a typo and may lead to unexpected behaviours.
12+
/// It's most probably a typo and may lead to unexpected behaviours.
1313
/// ### Example
1414
/// ```rust
1515
/// let x = 3_i32 ^ 4_i32;

0 commit comments

Comments
 (0)