Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

perhaps, char8_t is best avoided, until 2025? (was 2023) #22

Open
DBJDBJ opened this issue May 7, 2021 · 1 comment
Open

perhaps, char8_t is best avoided, until 2025? (was 2023) #22

DBJDBJ opened this issue May 7, 2021 · 1 comment
Assignees
@DBJDBJ
Labels
question

Comments

@DBJDBJ
Copy link
Collaborator

DBJDBJ commented May 7, 2021

"...C++20 keyword char8_t brings (at last) the UTF-8 to the C++..."

https://dbj.org/c-char8_t-is-broken/

There is a lot to read, but the first few paragraphs are enough.
@DBJDBJ DBJDBJ added the question label May 7, 2021
@DBJDBJ DBJDBJ self-assigned this May 7, 2021
@DBJDBJ DBJDBJ changed the title oerhaps, char8_t is best avoided, until 2023 perhaps, char8_t is best avoided, until 2023 ? May 7, 2021
@frederick-vs-ja
Copy link

char8_t has already broken some things... However, for a JSON library, have you found any problem of which a fix will be breaking, if we instantly adopt char8_t?

P2626R0 seems related. It's unclear to me whether the functionalities it proposed are implementable.

@DBJDBJ DBJDBJ changed the title perhaps, char8_t is best avoided, until 2023 ? perhaps, char8_t is best avoided, until 2025? (was 2023) Jul 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DBJDBJ DBJDBJ

Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DBJDBJ @frederick-vs-ja