-
-
Notifications
You must be signed in to change notification settings - Fork 146
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
Read Write for core #51
Comments
@Ericson2314 I'd be willing to do so once |
I'm going to close this but feel free to re-open if you think we should reconsider core-io! |
Sure. Once I have a version on crates.io polished a bit I'll ping this. |
@BurntSushi Chiming in as I'm using core_io a bunch: I would very much like this to happen, but until jethrogb/rust-core_io#3 is resolved this would make the life of downstream crates harder. |
@whitequark That library is distinct from the one @Ericson2314 linked. |
@BurntSushi Oh. I'm much less happy with Ericson2314's library because it misses basic things (e.g. |
FWIW the only reason there is no BufReader is because I haven't implemented it yet. |
Yes, that you are reimplementing parts that are already well-tested by virtue of shipping in std::io also bothers me. |
@Tobba and I have worked on https://github.com/QuiltOS/core_io, a copy of Read and Write but with an associated error type to make it just need core. Perhaps it would be nice to (optionally) extend these traits for no_std users?
The text was updated successfully, but these errors were encountered: