Tracking Issue for allowing comparisons between `CStr`, `CString`, and `Cow<CStr>`.

[bjoernager]

Feature gate: #![feature(c_string_eq_c_str)]

This is a tracking issue for extending the possible comparisons between CStr, CString, and Cow<CStr>.

Public API

// core::ffi

impl PartialEq<&Self> for CStr;

impl PartialEq<CString> for CStr;

impl PartialEq<Cow<'_, Self>> for CStr;

// alloc::ffi

impl PartialEq<CStr> for CString;

impl PartialEq<&CStr> for CString;

impl PartialEq<Cow<'_, CStr>> for CString;

// alloc::borrow

impl PartialEq<CStr> for Cow<'_, CStr>;

impl PartialEq<&CStr> for Cow<'_, CStr>;

impl PartialEq<CString> for Cow<'_, CStr>;

Steps / History

• API Change Proposal (ACP): #517
• Implementation: Allow comparisons between CStr, CString, and Cow<CStr>. #137268

Unresolved Questions

• None yet.

[qmwrygdxpzc]

Now the CStr type can compare against &CStr. The str type can't compare against &str. Is there a plan to add the feature to the str type?

[bjoernager]

I'll admit that I actually overlooked that behaviour not being present with str. Nonetheless, the existing convention was to implement both PartialEq<str> and PartialEq<&str> for string-like types, so applying it to str as well seems reasonable.