-
Notifications
You must be signed in to change notification settings - Fork 13.4k
std::io should re-export more sub-items #11119
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
Comments
Nominating, if we decide to make submodules private this is a backwards-compatibility issue. |
If the standard library is going to lean more heavily on reexports, it'd be nice to figure out some way of better presenting the documentation for the reexported items. Currently, I think it ends up living in the module it was defined in, even if that module isn't reachable. This ends up being confusing since you see documentation at a path that you can't import. |
Accepted for 1.0, P-backcompat-libs. |
* Reexport io::mem and io::buffered structs directly under io, make mem/buffered private modules * Remove with_mem_writer * Remove DEFAULT_CAPACITY and use DEFAULT_BUF_SIZE (in io::buffered) cc #11119
We're exporting a lot now. What's left? |
Many of the utilities are currently being reexported, but very few of the I/O primitives other than This issue is becoming quite vague, however, so I think that I'm going to close this in favor of more specific issues targeting the modules that I still have in mind. |
It's a little annoying to import
buffered::BufferedReader
andmem::MemWriter
. It'd be really nice if the imports werestd::io::BufferedReader
andstd::io::MemWriter
.If possible, I would also like to make both the
mem
/buffered
and whatever other modules are re-exported private.The text was updated successfully, but these errors were encountered: