-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Tracking issue for 'more_io_inner_methods' #41519
Comments
I'd like to propose that this be stabilized for 1.20. The added methods are rather uncontroversial: they simply expose the same type of behavior already exposed by other structures. As such, stabilizing these has little to no drawback. @brson, @alexcrichton |
@rfcbot fcp merge |
Team member @alexcrichton has proposed to merge this. The next step is review by the rest of the tagged teams: No concerns currently listed. Once these reviewers reach consensus, this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period is now complete. |
Stabilization PR is incoming. |
Stabilize 'more_io_inner_methods' feature. As in the title. Closes #41519.
Feature was added in #41463, resolving #29067.
This feature enables several internal accessor methods on structures in
std::io
includingTake::{get_ref, get_mut}
andChain::{into_inner, get_ref, get_mut}
.cc @alexcrichton
The text was updated successfully, but these errors were encountered: