From ff244b6c43163385a3c94a0a27ce7fefa1d1f4c4 Mon Sep 17 00:00:00 2001 From: Jean Mertz Date: Fri, 3 May 2019 17:38:13 +0200 Subject: [PATCH] Fix link in into_iter_on_array documentation The non-inline variant wasn't being rendered correctly. see: https://rust-lang.github.io/rust-clippy/master/index.html#into_iter_on_array --- clippy_lints/src/methods/mod.rs | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/clippy_lints/src/methods/mod.rs b/clippy_lints/src/methods/mod.rs index 4f8d29a88d6..2cf73433b05 100644 --- a/clippy_lints/src/methods/mod.rs +++ b/clippy_lints/src/methods/mod.rs @@ -781,8 +781,9 @@ declare_clippy_lint! { /// their content into an iterator. Auto-referencing resolves the `into_iter` call to its reference /// instead, like `<&[T; N] as IntoIterator>::into_iter`, which just iterates over item references /// like calling `iter` would. Furthermore, when the standard library actually - /// [implements the `into_iter` method][25725] which moves the content out of the array, the - /// original use of `into_iter` got inferred with the wrong type and the code will be broken. + /// [implements the `into_iter` method](https://github.com/rust-lang/rust/issues/25725) which moves + /// the content out of the array, the original use of `into_iter` got inferred with the wrong type + /// and the code will be broken. /// /// **Known problems:** None /// @@ -791,8 +792,6 @@ declare_clippy_lint! { /// ```rust /// let _ = [1, 2, 3].into_iter().map(|x| *x).collect::>(); /// ``` - /// - /// [25725]: https://github.com/rust-lang/rust/issues/25725 pub INTO_ITER_ON_ARRAY, correctness, "using `.into_iter()` on an array"