maybe I was doing it wrong but that's the type I used (array list of u32's) when implementing a text box in a gui
-
-
-
Why not UTF-8 or UTF-16?
- 2 more replies
New conversation -
-
-
For people who store UTF32 code points as their in-memory representation of text.
-
But why would you do that?
- 9 more replies
New conversation -
-
-
My guess would be to store already-parsed code points and process them more easily. I know, you still have to compose certain characters, but it's less often. My more important question is: Why are u8string and u16string still so useless?
-
But why would you do that? Memory is more expensive than ALU.
- 1 more reply
New conversation -
-
-
So you can store a parallel array of i11 in the unused bits
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
must be for intensive emoji processing

Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Because there is no method of string handling so bad that it's not worth a shot.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It serves the one of very few mechanism to parse UTF-8 string only with STL https://en.cppreference.com/w/cpp/locale/codecvt_utf8 … There is u8string and u16string but they are just basic_string<char16_t> which are not unicode aware. They can’t even iterate through characters.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.