From b363f130698dbc55fe594155bcb4df826ffad71e Mon Sep 17 00:00:00 2001 From: Jeff Date: Fri, 4 Mar 2022 09:48:51 -0500 Subject: [PATCH] Add suggested changes to the docs --- library/core/src/iter/traits/collect.rs | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/library/core/src/iter/traits/collect.rs b/library/core/src/iter/traits/collect.rs index 28ae2277252..dee66e6e072 100644 --- a/library/core/src/iter/traits/collect.rs +++ b/library/core/src/iter/traits/collect.rs @@ -5,9 +5,9 @@ /// collection of some kind. /// /// If you want to create a collection from the contents of an iterator, the -/// [`Iterator::collect()`] method is preferred. However, the compiler is -/// sometimes unable to infer the full type of the collection. In these cases, -/// [`FromIterator::from_iter()`] can be more concise and readable. See the +/// [`Iterator::collect()`] method is preferred. However, when you need to +/// specify the container type, [`FromIterator::from_iter()`] can be more +/// readable than using a turbofish (e.g. `::>()`). See the /// [`Iterator::collect()`] documentation for more examples of its use. /// /// See also: [`IntoIterator`].