rust-lang / rust-lang/rust

Tracking Issue for `casefold`

Open
#157,000 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-Unicode C-tracking-issue S-tracking-needs-to-bake T-libs
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

Feature gate: #![feature(casefold)]

This is a tracking issue for Unicode-aware case folding APIs in the standard library. These APIs do not perform NFC/NFKC normalization.

Public API
// `core`

impl char {
    pub fn to_casefold_unnormalized(self) -> ToCasefold;
}

mod char {
    #[derive(Debug, Clone)]
    pub struct ToCasefold { … };
    impl Iterator for ToCasefold {
        type Item = char;
        …
    }
    impl DoubleEndedIterator for ToCasefold { … }
    impl FusedIterator for ToCasefold {}
    impl ExactSizeIterator for ToCasefold {}
    impl fmt::Display for ToCasefold { … }
}

impl str {
    pub fn eq_ignore_case_unnormalized(&self, other: &str) -> bool;
}
// `alloc`

impl str {
    pub fn to_casefold_unnormalized(&self) -> String;
}
Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

  • Implementation: #154742
  • Final comment period (FCP)^1
  • Stabilization PR
Unresolved Questions

@rustbot label A-Unicode

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing implementation PR #154742 and the listed public APIs behind the #![feature(casefold)] gate. Resolve the open question about normalization, then follow the FCP and stabilization steps; done means the unresolved concerns are addressed and a stabilization PR is completed.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
internationalization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.