Tracking Issue for inherent_ascii_escape

[clarfonthey]

Feature gate: #![feature(inherent_ascii_escape)]

Public API

impl u8 {
    pub fn escape_ascii(self) -> core::ascii::EscapeDefault;
}

impl [u8] {
    pub fn escape_ascii(&self) -> EscapeAscii<'_>;
}

// core::slice
pub struct EscapeAscii<'a>;

Steps / History

• Implementation: Add escape_ascii method to u8 and [u8] #73111 escape_ascii take 2 #83130
• Final commenting period (FCP)
• Stabilization PR

Unresolved Questions

• Naming. escape_ascii, escape_default, ascii_escape_default, ... ?
• Deprecate std::ascii::escape_default? (That is, all of std::ascii.)

[tesuji]

typo: inherent_ascii_escpe

[tanriol]

What's the status of this? Is it ready for stabilization or waiting for something?

[joshtriplett]

This seems reasonable to me, and it seems to work as advertised.

Shall we stabilize these escape_ascii() methods?

@rfcbot merge

[rfcbot]

Team member @joshtriplett 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
• @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. 🔔

[clarfonthey]

One thing that wasn't mentioned in FCP: should stabilising this also lead to deprecating the std::ascii module? Since the naming seems to be fine re: the first unresolved question, but there's the one about deprecation as well.