Skip to content

Tracking Issue for utf8_chunks #99543

@dylni

Description

@dylni

Feature gate: #![feature(utf8_chunks)]

This is a tracking issue for an improved API for str::from_utf8.

Public API

// core::str pub struct Utf8Chunks<'a> { ... } impl<'a> Utf8Chunks<'a> { pub fn new(bytes: &'a [u8]) -> Self; } impl<'a> Iterator for Utf8Chunks<'a> { type Item = Utf8Chunk<'a>; } impl<'a> Clone for Utf8Chunks<'a>; impl<'a> Debug for Utf8Chunks<'a>; impl<'a> FusedIterator for Utf8Chunks<'a>; pub struct Utf8Chunk<'a> { ... } impl<'a> Utf8Chunk<'a> { pub fn valid(&self) -> &'a str; pub fn invalid(&self) -> &'a [u8]; } impl<'a> Clone for Utf8Chunk<'a>; impl<'a> Debug for Utf8Chunk<'a>; impl<'a> PartialEq for Utf8Chunk<'a>; impl<'a> Eq for Utf8Chunk<'a>;

Steps / History

Unresolved Questions

  • Should the constructor be Utf8Chunks::new or <[u8]>::utf8_chunks?
  • Should Utf8Chunks::debug or a similar method be exposed?

Footnotes

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.finished-final-comment-periodThe final comment period is finished for this PR / Issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions