Tracking Issue for `PathBuf::into_string`

Feature gate: #![feature(pathbuf_into_string)]

This is a tracking issue for rust-lang/libs-team#307

Currently, to convert a PathBuf into a String, you had to first use PathBuf::into_os_string and then OsString::into_string. However, with this feature, you can convert a PathBuf directly into a String using PathBuf::into_string, allowing you to not need to write the intermediate PathBuf::into_os_string.

Public API

// use std::path::Pathbuf; 

impl PathBuf {
    pub fn into_string(self) -> Result<String, PathBuf> { ... }
}

Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

• ACP: rust-lang/libs-team#307
• Implementation: #156204
• Final comment period (FCP)^1
• Stabilization PR: #156840

Unresolved Questions

• None yet.

Start with the PathBuf::into_string public API and the pathbuf_into_string feature gate described here, then review implementation PR #156204 and stabilization PR #156840. The feature is complete when stabilization has no unresolved questions and the API is accepted through the documented feature lifecycle.