Tracking Issue for String::into_chars

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.

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

Rollup merge of rust-lang#133057 - tisonkun:into-chars, r=Amanieu

Unrolled build for rust-lang#133057

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

Rollup merge of rust-lang#133057 - tisonkun:into-chars, r=Amanieu

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>.

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.

Navigation Menu

Repository navigation

Tracking Issue for String::into_chars #133125

Public API

Steps / History

Unresolved Questions

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Tracking Issue for String::into_chars #133125

Description

Public API

Steps / History

Unresolved Questions

Footnotes

Activity

YkdWaWEzVmphR1Z1 commented on Mar 3, 2025

tisonkun commented on Nov 18, 2025

WASDetchan commented on Mar 27, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions