4 points

I really doubt that such a large change can come before C++ lost all its momentum. (And you could even argue that that already has happened)

I’m currently stuck at work with C++14 as we need certain compiler qualifications (for safety in automotive). Even if that proposal would be in C++26 I could maybe use it in 2035 ($current_year - 2014 + 2026). In 2035 I doubt anyone in that domain will still write C++ as Rust is already making headway.

permalink
report
reply
1 point

I definitely gave up on C++ when trying to refresh on it you’re me too go learn C++8 before jumping in to 14.

If learning something requires learning an old version of it before moving on to the current version, something went very wrong.

permalink
report
parent
reply
2 points

It is perfectly ok to start with C++14, in fact probably preferable to starting with anything before C++11. The idioms changed a lot in C++11. I think changes since then have been minor and incremental by comparison.

permalink
report
parent
reply
1 point

Sure, today it is. In 2014, though, that wasn’t the advice.

permalink
report
parent
reply
3 points

I don’t think it’s possible to make C++ safe without strictly limiting the user program to a subset of the language. There are guidelines for that (https://github.com/isocpp/CppCoreGuidelines) but even when I try to code in that style, I get to debug crashes the usual way. C++ makes some optimizations possible through e.g. move semantics that are absent from Rust and Ada but I wonder if it really matters these days. Rust seems to be displacing C++ for lots of new projects going forward.

permalink
report
reply

C & C++

!cpp@lemmy.ml

Create post

Community stats

  • 19

    Monthly active users

  • 73

    Posts

  • 41

    Comments

Community moderators