Tracking Issue for IntoInnerError::into_parts etc. (io_into_inner_error_parts)

[ijackson]

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

• https://doc.rust-lang.org/nightly/std/io/struct.IntoInnerError.html#method.into_parts
• https://doc.rust-lang.org/nightly/std/io/struct.IntoInnerError.html#method.into_error

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 Provide IntoInnerError::into_parts #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.

[dtolnay]

@rust-lang/libs
@rfcbot fcp merge

Check out @ijackson's recap of this API in #84770 (comment).

[rfcbot]

Team member @dtolnay has proposed to merge this. The next step is review by the rest of the tagged team members:

• @Amanieu
• @BurntSushi
• @dtolnay
• @joshtriplett
• @m-ou-se
• @sfackler
• @yaahc

No concerns currently listed.

Once a majority of reviewers approve (and at most 2 approvals are outstanding), 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.

[rfcbot]

🔔 This is now entering its final comment period, as per the review above. 🔔