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

[DBJDBJ]

"...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.

[frederick-vs-ja]

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.