@@ -1815,7 +1815,7 @@ declare_lint! {
18151815
18161816declare_lint ! {
18171817 /// The `irrefutable_let_patterns` lint detects detects [irrefutable
1818- /// patterns] in [if- let] and [while- let] statements.
1818+ /// patterns] in [`if let` ] and [` while let` ] statements.
18191819 ///
18201820 ///
18211821 ///
@@ -1832,7 +1832,7 @@ declare_lint! {
18321832 /// ### Explanation
18331833 ///
18341834 /// There usually isn't a reason to have an irrefutable pattern in an
1835- /// if- let or while- let statement, because the pattern will always match
1835+ /// `if let` or ` while let` statement, because the pattern will always match
18361836 /// successfully. A [`let`] or [`loop`] statement will suffice. However,
18371837 /// when generating code with a macro, forbidding irrefutable patterns
18381838 /// would require awkward workarounds in situations where the macro
@@ -1843,14 +1843,14 @@ declare_lint! {
18431843 /// See [RFC 2086] for more details.
18441844 ///
18451845 /// [irrefutable patterns]: https://doc.rust-lang.org/reference/patterns.html#refutability
1846- /// [if- let]: https://doc.rust-lang.org/reference/expressions/if-expr.html#if-let-expressions
1847- /// [while- let]: https://doc.rust-lang.org/reference/expressions/loop-expr.html#predicate-pattern-loops
1846+ /// [`if let` ]: https://doc.rust-lang.org/reference/expressions/if-expr.html#if-let-expressions
1847+ /// [` while let` ]: https://doc.rust-lang.org/reference/expressions/loop-expr.html#predicate-pattern-loops
18481848 /// [`let`]: https://doc.rust-lang.org/reference/statements.html#let-statements
18491849 /// [`loop`]: https://doc.rust-lang.org/reference/expressions/loop-expr.html#infinite-loops
18501850 /// [RFC 2086]: https://github.com/rust-lang/rfcs/blob/master/text/2086-allow-if-let-irrefutables.md
18511851 pub IRREFUTABLE_LET_PATTERNS ,
18521852 Warn ,
1853- "detects irrefutable patterns in if- let and while- let statements"
1853+ "detects irrefutable patterns in `if let` and ` while let` statements"
18541854}
18551855
18561856declare_lint ! {
0 commit comments