Tracking Issue for CStr::is_empty

[jmillikin]

Feature gate: #![feature(cstr_is_empty)]

This is a tracking issue for adding an is_empty() method to core::ffi::CStr.

ACP: rust-lang/libs-team#106

Public API

// core::ffi

impl CStr {
	pub const fn is_empty(&self) -> bool;
}

Steps / History

• Implementation: Add is_empty() method to core::ffi::CStr. #102445
• Final comment period (FCP)¹
• Stabilization PR: Stabilize feature cstr_is_empty #111043

Unresolved Questions

• None yet.

Footnotes

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

[jmillikin]

Gentle ping for @rust-lang/libs-api -- would it be possible to start the FCP now? I don't think there's much API surface to review.

[jmillikin]

(pinging someone from the libs team, per instructions at https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html)

@cuviper I'd like to start the FCP for this feature. The new method has been in nightly since v1.66, and it'd be nice to have it in stable.

[jmillikin]

Timed out waiting for someone to start the FCP -- since there's not much to discuss regarding the API, I sent in PR #111043 to stabilize.

[BurntSushi]

@rfcbot fcp merge

[rfcbot]

Team member @BurntSushi 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.