modern-cpp-features VS cppfront

Just go through this https://github.com/AnthonyCalandra/modern-cpp-features and you should be fine.

If you also like thorough explanations and graphs, there's https://hackingcpp.com/ that could answer many questions you might have.

By the way, just in case, bookmark this online C++ reference https://eel.is/c++draft/ for diving in deep waters.

Good luck!

I'm a little 10 years out from writing C++ professionally and I found this cheat sheet[0] useful. Basically if you have an inkling of the concept you're looking for, just search on that cheat sheet to find the relevant new C++ thing. Specifically for me, we used Boost for smart pointers which are now part of the stdlib, and threads are now part of the stdlib as well.

[0] https://github.com/AnthonyCalandra/modern-cpp-features

A more productive way to go about it would be to ask "What are the features in each version of C++ past C++11 that I should care about the most?" instead. In that case you could take a look at things like https://github.com/AnthonyCalandra/modern-cpp-features and https://github.com/mortennobel/cpp-cheatsheet, see what appeals to you, ignore what does not.

Looks like there's a version history here

As someone suggested cppcon and c++ talks, also I would reccomend reading this: https://github.com/AnthonyCalandra/modern-cpp-features and all things in the papers section in this: https://en.cppreference.com/w/cpp/compiler_support

I've already done a bit of research which has led me to the The Definitive C++ Book Guide & List. From that, I've decided to go over The C++ Programming Language (4th Edition) to learn C++11 and then this GitHub repo to learn the remaining C++14/17/20 features.

clickable:

"Welcome back to C++ - Modern C++" https://learn.microsoft.com/en-us/cpp/cpp/welcome-back-to-cp...

"21 New Features of Modern C++ to Use in Your Project" http://www.vishalchovatiya.com/21-new-features-of-modern-cpp...

"What is modern C++"? https://www.reddit.com/r/cpp_questions/comments/tgs6ir/what_...

"C++ is the next C++" https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p26...

"modern c++ features" https://github.com/AnthonyCalandra/modern-cpp-features

C++ 23 to introduce module support "https://www.infoworld.com/article/3662808/c-plus-plus-23-to-..."

"C++ 2023" https://en.wikipedia.org/wiki/C%2B%2B23

> And I'm left wondering, is this just how C++ is? Can't the language provide tooling for me to better adhere to its guidelines

Well, first, the language can't provide tooling: C++ is defined formally, not through tools; and tools are not part of the standard. This is unlike, say, Rust, where IIANM - so far, Rust has been what the Rust compiler accepts.

But it's not just that. C++ design principles/goals include:

* multi-paradigmatism;

* good backwards compatibility;

* "don't pay for what you don't use"

and all of these in combination prevent baking in almost anything: It will either break existing code; or force you to program a certain way, while legitimate alternatives exist; or have some overhead, which you may not want to pay necessarily.

And yet - there are attempts to "square the circle". An example is Herb Sutter's initiative, cppfront, whose approach is to take in an arguably nicer/better/easier/safer syntax, and transpile it into C++ :

https://github.com/hsutter/cppfront/

I’m not fond of adding an increasing number of specific compiler options for memory-safety. I love -faddress=sanitizer or -fsanitize. But the historically growing number of warning which need to be turned on is an issue. For example the options -Wconversion, -Wsign-conversion and -Warith-conversion shall be default with C++26. And if your code doesn’t compile use either an older revision or turn it deliberately off (saying: I’m aware, read the handbook, I take the risk).

I want some of not all the ideas of CPP2/cppfront[1] in C++XX. Finally using #unsafe when needed, like Rust. C++ does evolve over decades, more like other languages.

[1] https://github.com/hsutter/cppfront

CPP2/cppfront:

https://github.com/hsutter/cppfront

I hope we see this in C++26 as optional mode i.e. #safe and #unsafe and same for #impdef or so.

C++23 is done. But C++ is not! In this talk, the author shares his personal perspectives on an ongoing and very active evolution of C++, updates on his cppfront experimental compiler, and why compatibility is essential to the further success of the C++ development.

https://github.com/hsutter/cppfront

But his side project at Microsoft didn't gain traction with gcc, clang, etc and everybody else in the industry. So at this point, the C++ committee will be perceived as "so far behind" ... because there's nothing for them to vote on.