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.

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

TRPL: minor correction on how chars().nth() work #27611

Merged
merged 1 commit into from
Aug 11, 2015

Conversation

vincentbernat
Copy link
Contributor

The previous wording was confusing. While would we need to go through
the whole list just to find the first code point? chars() being an
iterator, we only need to walk from the beginning of the list.

Note that I am not a native English speaker and I have still difficulties to spot if a "the" is needed somewhere. Feel free to take this PR as a mere suggestion.

r? @steveklabnik

The previous wording was confusing. While would we need to go through
the whole list just to find the first code point? `chars()` being an
iterator, we only need to walk from the beginning of the list.
@rust-highfive
Copy link
Collaborator

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @steveklabnik (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@steveklabnik
Copy link
Member

This is great! your English is perfect. Thanks so much.

@steveklabnik
Copy link
Member

@bors: r+ rollup

@bors
Copy link
Contributor

bors commented Aug 9, 2015

📌 Commit b67adbe has been approved by steveklabnik

bors added a commit that referenced this pull request Aug 9, 2015
…labnik

The previous wording was confusing. While would we need to go through
the whole list just to find the first code point? `chars()` being an
iterator, we only need to walk from the beginning of the list.

Note that I am not a native English speaker and I have still difficulties to spot if a "the" is needed somewhere. Feel free to take this PR as a mere suggestion.

r? @steveklabnik
@bors
Copy link
Contributor

bors commented Aug 9, 2015

⌛ Testing commit b67adbe with merge 1d74121...

@bors
Copy link
Contributor

bors commented Aug 9, 2015

💔 Test failed - auto-linux-32-opt

@steveklabnik
Copy link
Member

@bors: retry

@bors
Copy link
Contributor

bors commented Aug 9, 2015

💔 Test failed - auto-linux-32-opt

@dotdash
Copy link
Contributor

dotdash commented Aug 10, 2015

@bors retry

Manishearth added a commit to Manishearth/rust that referenced this pull request Aug 11, 2015
…r, r=steveklabnik

The previous wording was confusing. While would we need to go through
the whole list just to find the first code point? `chars()` being an
iterator, we only need to walk from the beginning of the list.

Note that I am not a native English speaker and I have still difficulties to spot if a "the" is needed somewhere. Feel free to take this PR as a mere suggestion.

r? @steveklabnik
bors added a commit that referenced this pull request Aug 11, 2015
@bors bors merged commit b67adbe into rust-lang:master Aug 11, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants