2 ms·
While I share the sentiment, compare C#14 with C# 1.0, Java 25 with Java 1.0, Python 3.14 with Python 1.0. While C++ might be worse, when you have 300+ doing p
by pjmlp 10mo ago
While I share the sentiment, compare C#14 with C# 1.0, Java 25 with Java 1.0, Python 3.14 with Python 1.0.
While C++ might be worse, when you have 300+ doing proposals every three years, others aren't safer from similar churn, even if on smaller volume, and trying to keep backwards compatibility going.
And we all know what happened in Python.
Also Rust editions contrary to what many think, only cover a specific set of language evolution scenarios, it isn't anything goes, nor there is support for binary libraries.
As for a better C++, contrary to C, where it is business as usual, there are actually people trying to sort things out on WG21, even if isn't as well as we would like to.
"Making C++ Safe, Healthy, and Efficient - CppCon 2025"
https://youtu.be/p52mNWsh-qs?si=AEs1dtr6_iknzATv https://youtu.be/p52mNWsh-qs?si=AEs1dtr6_iknzATv
- gpm 10mo ago> nor there is support for binary libraries. This is a weird call-out because it's both completely incorrect and completely irrelevant to the larger point. Rust absolutely supports binary libraries. The only way to use a rust library with the current rust compiler is to first compile it to a binary format and then link to it. More so than C++ where header files (and thus generics via templates) are textual. Cargo, the most common build system for rust, insists on compiling every library itself (with narrow exceptions - that include for instance the precompiled standard library that is used by just about everyone). That's just a design choice of cargo, not the language.
- pjmlp 10mo agoRust does, Rust editions do not have a story for them.
- gpm 10mo agoThe story is that it must not matter which edition a library was compiled with - it's the boundary layer at which different editions interoperate with eachother.
- pjmlp 10mo agoProvided everything is available in source code, there are no semantic changes on the boundary level, or standard library types being used on the library public API that changed across editions.
- gpm 10mo agoNo. Not provided any of that. Must not matter really does mean "must not matter" here.