Tracking Issue for IntoInnerError::into_parts etc. (io_into_inner_error_parts) ·...
source link: https://github.com/rust-lang/rust/issues/79704
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Copy link
Contributor
ijackson commented on Dec 4, 2020 •
This is a tracking issue for std::io::IntoInnerError::into_parts and ::into_error.
The feature gate for the issue is #![feature(io_into_inner_error_parts)].
Public API
About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
- Implement these methods - see #79673
- Adjust documentation
- Stabilization PR (see instructions on rustc-dev-guide)
Unresolved Questions
These new methods are being introduced as an unstable feature to give time to validate their names, types, and documentation, before stabilisation.
Implementation history
Implementation (with docs) is in #79673, currently in review/rework.
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK