Tracking Issue for feature(core_c_str) and feature(alloc_c_string)

[joshtriplett]

Feature gate: #![feature(core_c_str)] and #![feature(alloc_c_string)]

This is a tracking issue for the availability of CStr in core and CString in alloc.

Public API

// core::ffi
pub struct CStr;
pub struct FromBytesWithNulError;

// alloc::ffi
pub struct CString;
pub struct NulError;
pub struct FromVecWithNulError;
pub struct IntoStringError;

Steps / History

• Implementation: library: Move CStr to libcore, and CString to liballoc #94079
• Final comment period (FCP)
• Stabilization PR

[joshtriplett]

core::ffi::c_* appears to be on track to stabilize in 1.63.0. Shall we do the same for core::ffi::CStr and alloc::ffi::CString?

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

[mbartlett21]

If this ends up being done, will the type aliases in std be changed back to re-exports?

[rfcbot]

The final comment period, with a disposition to merge, as per the review above, is now complete.

As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed.

This will be merged soon.