File tree Expand file tree Collapse file tree 1 file changed +3
-4
lines changed Expand file tree Collapse file tree 1 file changed +3
-4
lines changed Original file line number Diff line number Diff line change @@ -781,8 +781,9 @@ declare_clippy_lint! {
781781 /// their content into an iterator. Auto-referencing resolves the `into_iter` call to its reference
782782 /// instead, like `<&[T; N] as IntoIterator>::into_iter`, which just iterates over item references
783783 /// like calling `iter` would. Furthermore, when the standard library actually
784- /// [implements the `into_iter` method][25725] which moves the content out of the array, the
785- /// original use of `into_iter` got inferred with the wrong type and the code will be broken.
784+ /// [implements the `into_iter` method](https://github.com/rust-lang/rust/issues/25725) which moves
785+ /// the content out of the array, the original use of `into_iter` got inferred with the wrong type
786+ /// and the code will be broken.
786787 ///
787788 /// **Known problems:** None
788789 ///
@@ -791,8 +792,6 @@ declare_clippy_lint! {
791792 /// ```rust
792793 /// let _ = [1, 2, 3].into_iter().map(|x| *x).collect::<Vec<u32>>();
793794 /// ```
794- ///
795- /// [25725]: https://github.com/rust-lang/rust/issues/25725
796795 pub INTO_ITER_ON_ARRAY ,
797796 correctness,
798797 "using `.into_iter()` on an array"
You can’t perform that action at this time.
0 commit comments