Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I picked C++ back after a long break and I have to say in reasonably recent iterations (like C++17) it's good enough, although OOTB Unicode is a PAIN. They should have solved it in C++11 and moved on. It's a disgrace.


Does Carbon or c++next fix the ootb handling?


It's being actively worked on for C++2x. This video is a fairly recent update on how it's progressing: https://www.youtube.com/watch?v=AoLl_ZZqyOk

Note for those who are not used to C++Now talks: they are intented to be a bit more informal with regular interjections from the audience (who at C++Now are also often heavily involved in the development of the C++ standard), so don't think people are being rude by jumping in!


This is just an idea at this point. Ask again in 30 years.


Hopefully it's really good in the near future. https://thephd.dev/cuneicode-and-the-future-of-text-in-c




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: