-
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
String encoding/decoding and I/O #6164
Comments
Nominating, we need to deal with this. |
Big thread an this subject https://mail.mozilla.org/pipermail/rust-dev/2013-September/005503.html |
accepted for 1.0 in that we to at least define our story around this. documentation if nothing else. |
Last time @alexcrichton and I talked about this we concurred that encoding could be left to other libraries, and we don't need to explicitly solve this for 1.0. |
Nominating for removal from milestone. |
Removing from 1.0, P-high |
cc @aturon |
Assuming this is not very relevant these days. |
…arth Improve needless_collect output changelog: Improve needless_collect output Fixes rust-lang#6908 Partially addresses rust-lang#6164
How do we deal with string encoding of I/O? The existing implementation uses extension methods on Readers and Writers, but this is not sufficient because it doesn't maintain any state. Need a better understanding of the requirements here.
The text was updated successfully, but these errors were encountered: