|
|
Log in / Subscribe / Register

not really C++20

not really C++20

Posted May 1, 2026 18:44 UTC (Fri) by rgmoore (✭ supporter ✭, #75)
In reply to: not really C++20 by rolexhamster
Parent article: GCC 16.1 released

Compare this with the development and deployment model of languages likes Python and Rust. When Python 3.14 is released, we get the full implementation of Python 3.14, not a "theoretical" half-complete implementation of Python 3.14.

Yes, but you get the downside of that model, too. Python theoretically has a specification, but in practice what matters is what CPython does, not what the specification says. Also, the Python devs have an unfortunate habit of deprecating features that are still widely used, so code that was written a while ago may fail if it's run on a newer version. You win some, you lose some.


to post comments

not really C++20

Posted May 3, 2026 8:58 UTC (Sun) by cyperpunks (subscriber, #39406) [Link]

Rust follows the same model, multiple implementation is very useful, it helps to uncover mismatch between specification and implementation, for this reason gccrs is very important.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds