Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Chapter 3.5. - iter() method not explained. #2672

Closed
faraaz-baig opened this issue Mar 28, 2021 · 4 comments
Closed

Chapter 3.5. - iter() method not explained. #2672

faraaz-baig opened this issue Mar 28, 2021 · 4 comments
Labels
blocked upstream Blocked on a change that needs to happen in a different repo first Enhancement
Milestone
ch3

Comments

@faraaz-baig
Copy link

I am learning rust and I find every single line of code is explained properly. Great job! unfortunately was going through chapter 3.5 "Looping Through a Collection with for" section. The iter() method is not explained.

This is just to maintain consistency in quality of the rust docs :)
@tal-zvon
Copy link

tal-zvon commented Apr 3, 2021

There is an entire chapter that deals with iterators that follows (Chapter 13).

Chapter 3.5 just has a short example of how to iterate through the array. The chapter's focus is not iterators.
I think it should either be left as-is, or a short note can be added that says something like "we'll take a closer look at iterators in Chapter 13".

@faraaz-baig
Copy link
Author

A Short note will do a great job!

@carols10cents
Copy link
Member

Soon the iter method won't be needed in this example! https://blog.rust-lang.org/2021/05/11/edition-2021.html#intoiterator-for-arrays I'm leaving this issue open as we're going to fix this by removing iter when the new functionality is stable.

@carols10cents carols10cents added this to the ch3 milestone Jul 14, 2021
@carols10cents carols10cents added the blocked upstream Blocked on a change that needs to happen in a different repo first label Jul 14, 2021
@steveklabnik
Copy link
Member

(Yes, and this is part of the reason it wasn't explained; I didn't want to do a bunch here when it would eventually be unneeded, and most people seemed to intuitively get what was going on.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked upstream Blocked on a change that needs to happen in a different repo first Enhancement
Projects
None yet
Milestone
ch3
Development

No branches or pull requests
4 participants
@steveklabnik @carols10cents @tal-zvon @faraaz-baig