-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Add read_to_str and write_{str, line} #10861
Conversation
/// # Failure | ||
/// | ||
/// This function will raise all the same conditions as the `read` method, | ||
/// along with raising a condition if the input is not valid utf-8. |
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.
The capitalisation of utf-8
is inconsistent.
Bump. I would love to have these methods back. I was using them before they disappeared, and the documentation in |
Agreed with @huonw. r=me with those changes. |
These methods are sorely needed on readers and writers, and I believe that the encoding story should be solved with composition. This commit adds back the missed functions when reading/writing strings onto generic Readers/Writers.
These methods are sorely needed on readers and writers, and I believe that the encoding story should be solved with composition. This commit adds back the missed functions when reading/writing strings onto generic Readers/Writers.
Thanks for fixing this. I have just noticed that there also used to be |
Ah I guess I missed that! Pull requests are welcome though! I'll see if I can get around to it soon. |
I will try and send a pull request in the next day or two. |
new lint [`single_call_fn`] Closes rust-lang#10861 changelog: New lint [`single_call_fn`]
These methods are sorely needed on readers and writers, and I believe that the
encoding story should be solved with composition. This commit adds back the
missed functions when reading/writing strings onto generic Readers/Writers.