-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
fix more typos found by codespell. #48275
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @eddyb (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. Due to 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. |
src/libstd/io/buffered.rs
Outdated
@@ -293,7 +293,7 @@ impl<R: Seek> Seek for BufReader<R> { | |||
/// where `n` minus the internal buffer length overflows an `i64`, two | |||
/// seeks will be performed instead of one. If the second seek returns | |||
/// `Err`, the underlying reader will be left at the same position it would | |||
/// have if you seeked to `SeekFrom::Current(0)`. | |||
/// have if you sought to `SeekFrom::Current(0)`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might prefer rewording this, as "seek time" is a noun, and it's confusing if it's used as a verb like this. I agree that "seeked" is incorrect, but finding a different verb to use would be preferable.
Apart from the one comment, all the corrections here look good to me! |
@bors r+ rollup Thanks! |
📌 Commit 0a4cf97 has been approved by |
@bors r- Oops missed @varkor's nit at #48275 (review) |
0a4cf97
to
09e0d3b
Compare
src/libstd/io/buffered.rs
Outdated
@@ -293,7 +293,7 @@ impl<R: Seek> Seek for BufReader<R> { | |||
/// where `n` minus the internal buffer length overflows an `i64`, two | |||
/// seeks will be performed instead of one. If the second seek returns | |||
/// `Err`, the underlying reader will be left at the same position it would | |||
/// have if you seeked to `SeekFrom::Current(0)`. | |||
/// have if you had gotten to `SeekFrom::Current(0)`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cc @varkor ↑
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, didn't spot the change! I think something like: /// have if you called `seek` with `SeekFrom::Current(0)`.
would be more clear, as it describes the intention (seeking to SeekFrom::Current(0)
), rather than the implementation's behaviour.
09e0d3b
to
4452446
Compare
@@ -293,7 +293,7 @@ impl<R: Seek> Seek for BufReader<R> { | |||
/// where `n` minus the internal buffer length overflows an `i64`, two | |||
/// seeks will be performed instead of one. If the second seek returns | |||
/// `Err`, the underlying reader will be left at the same position it would | |||
/// have if you seeked to `SeekFrom::Current(0)`. | |||
/// have if you called `seek` with `SeekFrom::Current(0)`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, updated
Looks good to me! Thanks @matthiaskrgr! |
@bors r=kennytm,varkor Thanks again! |
📌 Commit 4452446 has been approved by |
…arkor fix more typos found by codespell.
…arkor fix more typos found by codespell.
No description provided.