Skip to content

[filesystems] Replace "encoded character type" with "character type" from the core wording#8158

Open
frederick-vs-ja wants to merge 3 commits intocplusplus:mainfrom
frederick-vs-ja:encoded-core-character-types
Open

[filesystems] Replace "encoded character type" with "character type" from the core wording#8158
frederick-vs-ja wants to merge 3 commits intocplusplus:mainfrom
frederick-vs-ja:encoded-core-character-types

Conversation

@frederick-vs-ja
Copy link
Copy Markdown
Contributor

The terms "encoded character type(s)" (introduced in [fs.req]) and "character type(s)" (introduced in [basic.fundamental]) mean exactly the same set of types. It's probably better to avoid such duplicate. And the current preference seems to be using "character type" throughout the library wording, rather than renaming the term in the core wording.

Closes #5638.

Copy link
Copy Markdown
Member

@jensmaurer jensmaurer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feels like a simplification.

@jwakely ?

@eisenwave eisenwave added the P3-Other Triaged issue not in P1 or P2 label Nov 6, 2025
@tkoeppe
Copy link
Copy Markdown
Contributor

tkoeppe commented Nov 15, 2025

See https://eel.is/c++draft/basic.fundamental#11.sentence-1 for characater types. @jwakely?

@tkoeppe
Copy link
Copy Markdown
Contributor

tkoeppe commented Nov 15, 2025

Could it be that the term "character type" was only introduced by https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p2314r4.html in 2021, long after the Filesystem wording was made? So maybe this is just missed cleanup

Comment thread source/iostreams.tex Outdated
Comment thread source/iostreams.tex Outdated
@tkoeppe tkoeppe added the changes requested Changes to the wording or approach have been requested and not yet applied. label Nov 17, 2025
@frederick-vs-ja frederick-vs-ja force-pushed the encoded-core-character-types branch from 3bd95fd to 2dc2735 Compare December 15, 2025 01:48
@frederick-vs-ja
Copy link
Copy Markdown
Contributor Author

@jwakely @tkoeppe Changed and rebased.

@frederick-vs-ja frederick-vs-ja force-pushed the encoded-core-character-types branch from 2dc2735 to 1364579 Compare December 15, 2025 02:04
@wg21bot wg21bot added the needs rebase The pull request needs a git rebase to resolve merge conflicts. label May 2, 2026
@frederick-vs-ja frederick-vs-ja force-pushed the encoded-core-character-types branch from 1364579 to 3a0c4c4 Compare May 6, 2026 02:10
@frederick-vs-ja
Copy link
Copy Markdown
Contributor Author

@jwakely @tkoeppe Rebased.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changes requested Changes to the wording or approach have been requested and not yet applied. needs rebase The pull request needs a git rebase to resolve merge conflicts. P3-Other Triaged issue not in P1 or P2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[basic.fundamental] Weird terminology about "X character types"

6 participants