Tracking Issue for String::into_chars

[tisonkun]

Feature gate: #![feature(string_into_chars)]

This is a tracking issue for:

• String::into_chars

Public API

impl String {
    pub fn into_chars(self) -> IntoChars {
        IntoChars { bytes: self.into_bytes().into_iter() }
    }
}

impl Iterator for IntoChars {
    type Item = char;
}

Steps / History

• ACP: Implement into_chars for String libs-team#268
• Implementation: Impl String::into_chars #133057
• Final comment period (FCP)¹
• Stabilization PR

Unresolved Questions

• None yet.

Footnotes

1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

[YkdWaWEzVmphR1Z1]

Why does IntoChars have an into_string method, when it has to do memmove.
Vec::IntoIter also does not have into_vec.

[tisonkun]

Why does IntoChars have an into_string method, when it has to do memmove. Vec::IntoIter also does not have into_vec.

See #133057 (comment).

For vec::IntoIter, you can already do .collect which also possibly avoid some alloc. See impl<T> SpecFromIter<T, IntoIter<T>> for Vec<T>.

[WASDetchan]

What's stopping the feature from starting the FPC? There are no unresolved questions, and the implementation has been in nightly for more than a year now, everything seems ready.