3 ms·
No one has ever said that Carbon will forever be frozen at C++17 compatibility. That's just the initial goal.
by TillE 4y ago
No 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)