3 ms·
"Fixing semantics" while keeping 100% ABI compatibility with old C++ seems really hard. It looks like this will have to allow for some kind of opt-in ABI break
by zozbot234 4y ago
"Fixing semantics" while keeping 100% ABI compatibility with old C++ seems really hard. It looks like this will have to allow for some kind of opt-in ABI breakage, at which point you're not far away from what you could achieve more easily by using e.g. Carbon, or just better Rust/C++ interop (see autocxx, crubit, creusot).
- deleted 4y ago[deleted]
- nsajko 4y ago> far away from what you could achieve more easily by using e.g. Carbon, or just better Rust/C++ interop (see creusot). At that point, why not just upgrade to C++20? Carbon, in particular, is left behind in the C++17 world, so it's outdated by C++20 (not to mention future developments).
- TillE 4y agoNo one has ever said that Carbon will forever be frozen at C++17 compatibility. That's just the initial goal.
- mgraczyk 4y agoGoogle is basically stuck in the C++17 world, so I wouldn't expect Carbon to move forward if they end up investing heavily in it. In particular Google hasn't even started to adopt C++ coroutines, threading, ranges, or modules (they have their own module implementation which is actually better in most ways, but different)
- MattPalmer1086 4y agoC++ doesn't define an ABI, even if particular tool chains try to preserve one.
- jcelerier 4y agoIn practice it has been stable on GCC, clang and msvc with their respective stdlibs since 2015. There are kids today learning programming with scratch that weren't born the last time ABI changed.
- MattPalmer1086 4y agoInteresting, thanks. I stopped using C++ before 2010. It remains my all time favourite language to do crazy stuff in, but I try to avoid crazy stuff these days!