Tracking Issue for `const_char_encode_utf16`

[bjoernager]

Feature gate: #![feature(const_char_encode_utf16)]

This is a tracking issue for supporting char::encode_utf16 in const scenarios.

Public API

impl char {
    pub const fn encode_utf16(self, dst: &mut [u16]) -> &mut [u16];
}

Steps / History

• Implementation: Support char::encode_utf16 in const scenarios. #130659
• Final comment period (FCP)
• Stabilization PR: Stabilise const_char_encode_utf16. #132153

Unresolved Questions

• None yet.

[bjoernager]

I don't think char::decode_utf16 currently can be implemented as const due to its dependence on IntoIterator.

[dtolnay]

@rfcbot fcp merge

Enabled by the recent stabilization of &mut in const (#129195).

[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

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