Skip to content

Extend core::char's documentation of casing issues#154491

Open
Jules-Bertholet wants to merge 3 commits intorust-lang:mainfrom
Jules-Bertholet:case-docs
Open

Extend core::char's documentation of casing issues#154491
Jules-Bertholet wants to merge 3 commits intorust-lang:mainfrom
Jules-Bertholet:case-docs

Conversation

@Jules-Bertholet
Copy link
Copy Markdown
Contributor

@rustbot label A-unicode A-docs

@rustbot rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue. labels Mar 28, 2026
@rustbot
Copy link
Copy Markdown
Collaborator

rustbot commented Mar 28, 2026

r? @Mark-Simulacrum

rustbot has assigned @Mark-Simulacrum.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

Why was this reviewer chosen?

The reviewer was selected based on:

  • Owners of files modified in this PR: @scottmcm, libs
  • @scottmcm, libs expanded to 8 candidates
  • Random selection from Mark-Simulacrum, scottmcm

@rustbot rustbot added A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools A-Unicode Area: Unicode labels Mar 28, 2026
@rust-log-analyzer

This comment has been minimized.

@Mark-Simulacrum
Copy link
Copy Markdown
Member

@Manishearth would you have some time to review the added content here, in particular the reference to icu-casemap being the right crate to point at?

I'm also not sure about the extensive documentation of the specific cases - it seems OK, but it also feels like it probably ought to already be documented somewhere in Unicode and maybe we can just link out to it? That would make me feel more confident it stays up to date over time.

@Jules-Bertholet
Copy link
Copy Markdown
Contributor Author

also feels like it probably ought to already be documented somewhere in Unicode and maybe we can just link out to it? That would make me feel more confident it stays up to date over time.

I wish lol. This information is widely dispersed between various Unicode data files, decade-old PDFs of proposals to the Unicode standards committee, Wayback Machine snapshots of defunct blogs, etc. I can link my sources if you would like, but as far as I am aware, there is no single authoritative prose resource we can direct users to for all this information.

Co-authored-by: GrigorenkoPV <GrigorenkoPV+github@yandex.ru>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools A-Unicode Area: Unicode S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-libs Relevant to the library team, which will review and decide on the PR/issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants