-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Improve the explanation about the behaviour of read_line #94957
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @dtolnay (or someone else) soon. Please see the contribution instructions for more information. |
6daa74a
to
7da07ff
Compare
r? @Dylan-DPC |
thanks @bors r+ rollup |
📌 Commit 2c06c86 has been approved by |
Rollup of 5 pull requests Successful merges: - rust-lang#94868 (Format core and std macro rules, removing needless surrounding blocks) - rust-lang#94951 (Extend the irrefutable_let_patterns lint to let chains) - rust-lang#94955 (Refactor: Use `format_args_capture` in some parts of `rustc_parse`) - rust-lang#94957 (Improve the explanation about the behaviour of read_line) - rust-lang#94974 (Ensure that `let_else` does not interact with `let_chains`) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
/// them to the provided buffer. You do not need to clear the buffer before | ||
/// appending. |
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 think this makes it sound more confusing than before.
You do not need to clear the buffer before appending.
This could be interpreted as: you don't need to clear it, because it happens automatically.
Note that rust-lang/book#2574 is about the Rust Book, not about the standard library documentation. The std documentation before this change already clearly states that this function appends the data.
Close issue like rust-lang/book#2574