Clarify BufRead::fill_buf doesn't consume data #150584
Open
+11
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The previous documentation said 'via Read methods' which incorrectly implied that fill_buf consumes the data. This restores the historical clarification that read() can return the same contents as fill_buf, and emphasizes the relationship with consume(). This addresses the concerns raised in the issue where implementations like BufReader and Cursor do not actually consume data when fill_buf is called - subsequent read() calls can still read the same bytes until consume() is explicitly called.
rustbot
added
S-waiting-on-review
Collaborator
|
r? @ChrisDenton rustbot has assigned @ChrisDenton. Use |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #149000
The previous documentation said 'via Read methods' which incorrectly implied that fill_buf consumes the data. This restores the historical clarification that read() can return the same contents as fill_buf, and emphasizes the relationship with consume().
This addresses the concerns raised in the issue where implementations like BufReader and Cursor do not actually consume data when fill_buf is called - subsequent read() calls can still read the same bytes until consume() is explicitly called.