And then the audience will nod yes, accept the message of what is possible, and go back to whatever approach they were doing already.
And then the audience will nod yes, accept the message of what is possible, and go back to whatever approach they were doing already.
At least in modern c++. Then again, modern C++ seems to play the same role as modern Java, in that some places use it but most of them are stuck at the version they picked when they started developing on a piece of software decades ago.
Turns out updating software versions in most companies is really hard, and updating humans atittude to specific programming practices even harder, unless their job is on the line.
And even so, it doesn't matter if IT says no, or the customer doesn't pay for consulting services to upgrade existing projects.
As for incompatible changes, there aren’t any in Rust by design. That limits some of the changes they can make even in an edition but in practice it works ok. Even over a longer time span, I think the Rust community will figure out a way to trim irrelevant cruft away.
I am not so optimistic when Rust achieves a similar market share and historical baggage, as C and C++ have today, growing since the 1970's.
It is of course better designed, and with better tooling, that doesn't spare it from market forces and companies sponsoring the foundation.
See where Linux foundation is today for a comparable example.
It isn't the typing, rather the culture.
Both Rust's OwnedFd and Rust's Mutex<T> have analogous C++ which are used, but lacking a borrowck C++ can't express the idea "Maximum of one person can have this"
What happens if I keep a mutable reference to the Goose despite unlocking the protective mutex? In C++ the answer is you lose mutual exclusion, in Rust that doesn't compile. C++ people will say "Don't do that" but "not doing that" does not scale whereas it doesn't compile scales just fine.
Static analysis in c++ is akin to clippy but without a --fix option and many more false positives. Also clippy is more about stylistic consistency within the ecosystem and completely optional, not about safety which isn’t optional.
Commercial tools like PVS and Coventry, or those used in high integrity computing, also allow for rule customisation.
However the first step is to use anything at all, a challenge since lint was born in 1979.