From bc33861c2240c966e01d6f3e0431d192c9c720c1 Mon Sep 17 00:00:00 2001 From: Jacob Pratt Date: Mon, 23 Aug 2021 20:02:17 -0400 Subject: [PATCH] Fix references to `ControlFlow` in docs --- library/core/src/iter/traits/iterator.rs | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/library/core/src/iter/traits/iterator.rs b/library/core/src/iter/traits/iterator.rs index 524d8f857e2a5..746548a96a477 100644 --- a/library/core/src/iter/traits/iterator.rs +++ b/library/core/src/iter/traits/iterator.rs @@ -1957,8 +1957,8 @@ pub trait Iterator { /// assert_eq!(it.next(), Some(&40)); /// ``` /// - /// While you cannot `break` from a closure, the [`crate::ops::ControlFlow`] - /// type allows a similar idea: + /// While you cannot `break` from a closure, the [`ControlFlow`] type allows + /// a similar idea: /// /// ``` /// use std::ops::ControlFlow; @@ -2024,8 +2024,8 @@ pub trait Iterator { /// assert_eq!(it.next(), Some("stale_bread.json")); /// ``` /// - /// The [`crate::ops::ControlFlow`] type can be used with this method for the - /// situations in which you'd use `break` and `continue` in a normal loop: + /// The [`ControlFlow`] type can be used with this method for the situations + /// in which you'd use `break` and `continue` in a normal loop: /// /// ``` /// use std::ops::ControlFlow;