Tracking Issue for `CStr::bytes`
Navigation Menu
{{ message }}
- Notifications You must be signed in to change notification settings
- Fork 14.6k
Open
Open
Labels
Description
opened
on May 30, 2023Feature gate: #![feature(cstr_bytes)]
This is a tracking issue for the CStr::bytes API.
Public API
impl CStr { pub fn bytes(&self) -> CStrBytes<'_>; } // core::ffi::c_str::Bytes pub struct Bytes<'a> { // ... } impl Iterator for Bytes<'_> { type Item = u8; // ... }
Steps / History
- API change proposal (ACP)1: ACP:
CStr::bytesiterator libs-team#135 - Implementation: Add CStr::bytes iterator #104353
-
impl Send + Syncand overridecountfor theCStr::bytesiterator #127444 - Final comment period (FCP)2
- Stabilization PR
Unresolved Questions
- Where should this type be located? This is discussed in ACP:
std::ffi::candstd::ffi::ossubmodules libs-team#134. (Resolution: Store incore::ffi::c_str.) - Should an
AsRef<CStr>andas_c_strmethod be added toCStrBytesto reflect theslice::IterAPI?
Footnotes
Metadata
Metadata
Assignees
No one assigned
Labels
Type
No type
Projects
No projects
Milestone
No milestone
Relationships
None yet
Development
No branches or pull requests
Issue actions