2 ms·
C++23 was finalized nearly six months ago so it is not correct to call C++20 the “latest spec”.
by akhosravian 3y ago
C++23 was finalized nearly six months ago so it is not correct to call C++20 the “latest spec”.
- LordDragonfang 3y agoI should have said the "latest standard", not "spec", if we're being technical. But EVERY bit of official material is very clear about asserting that C++23 is still a preview/in-progress, not a standard. Saying otherwise is, strictly speaking, incorrect. https://isocpp.org/std/the-standard https://isocpp.org/std/the-standard https://www.iso.org/standard/79358.html https://www.iso.org/standard/79358.html https://github.com/cplusplus/draft/blob/main/papers/n4951.md https://github.com/cplusplus/draft/blob/main/papers/n4951.md And quite frankly, what matters to devs is what tooling supports the specification without special configuration, and the answer is "basically none". Not a single compiler fully supports it. https://en.cppreference.com/w/cpp/compiler_support/23 https://en.cppreference.com/w/cpp/compiler_support/23 Also, side note, I'd be surprised if more than a third of C++ devs were even using C++20, based on last year's numbers showing only ~25% adoption: https://www.jetbrains.com/lp/devecosystem-2022/cpp/ https://www.jetbrains.com/lp/devecosystem-2022/cpp/