And the Winners are:

Last week, I launched a quiz. The price was it to win one of the five vouchers for the book “The Modern C++ Programming Cookbook” 2en Edition by Marius Bancila.

The challenge to win one of the five coupons was it to answer the following question: “What is your favorite C++ feature and why?.

Without further ado, here are the winners and there answers:

Samuel Burch
Oleh
José Braga
Idriss Chaouch
Daniel Garcia

The Answers

Samuel Burch

That’s pretty clear for me: ranges (and views). Not only is every STL container with C++20 automatically a range, but also do views allow a clean and pretty simple syntactic concatenation of operations to generate a new collection of desired items. Also one is very flexible by using lambdas in those filter operations. This has the [the] benefit of not having to rely on a fixed set of predefined operations.

Oleh

My favorite C++20 feature is : std:: source_location because it helps to understand where method was called or where exception was thrown. Other features are important too but it will be difficult to apply for big old projects and some features [can] be replaced external libraries, for example std:format -> fmt: format . Of course concepts and modules have big impact to C++ but it needs knowledge sharing between team members.

José Braga

I am in a company still attached to C++14. Using legacy C++ standards has been my professional experience ever since I became a C++ programmer 10y ago. I still remember fondly how Alien [this reference is important later on :)] it felt to program in C++11 and the excitement of going through the code to update the codebase to the new standard.

In my personal projects, I took full advantage of several C++17 features but the transition was easier, more familiar – It was a step forward, not a parkour ride.

Although daunting, going through a language overhaul is really exciting, filled with opportunities to learn and to expand the way we solve problems – sometimes also the way we think about our challenges.

Modernes C++ Mentoring

"Fundamentals for C++ Professionals" (open)

"Design Patterns and Architectural Patterns with C++" (open)

"C++20: Get the Details" (open)

"Concurrency with Modern C++" (open)

"Embedded Programming with Modern C++": January 2025

"Generic Programming (Templates) with C++": February 2025

"Clean Code: Best Practices for Modern C++": May 2025

Do you want to stay informed: Subscribe.

So, going through examples with Ranges is akin to jumping in the Nostromo to help Signourney Weaver fight off the ugly creature. Also it does not hurt that it borrows bash pipe — definitely my favorite :)

Idriss Chaouch

I really appreciate the concepts library defining in the header file. I’m a big fan of creating new types using behaviour at compile time.
Concepts introduce more flexibility to generic programming. Now it is possible to set restrictions on template parameters, check for constraints, and discover incompatible behaviour at compile time. Before this big feature introduced by C++20, we used Templates (and we still use Templates in some contexts), but Templates don’t only provide abstraction from the specific type, but also incorporate loose coupling between the entity and aggregate types.
Templates use the keyword “template”, Concepts go more further, they allow replacing it with a type description that describes the template parameter. If the type doesn’t satisfy the constraint, the compiler will then throw an error.
Concepts rely essentially on constraints. A constraint is a way to specify requirements for template arguments, and a concept is a set of constraints. We can also combine many concepts into one to get a new concept.
We can also find some more strength provided by the Concepts library like the atomic constraint, constraint normalization, etc..

Daniel Garcia

My favourite C++20 feature is concepts. They remove many obscure idioms usually involving SFINAE and enable_if. That is great! Sometimes (not always) they make error messages easier to understand. That is a nice side effect. But those are not the real reasons.

The reason why I love concepts so much is that they make it easy to express programmers intent in a meaningful way. I can express generic code and non-generic code much more in the same way. And I can teach generic programming in a way that is meaningful to much more people.

Remaining Procedure

Congratulations to all Winners. I give Packt your e-mail address and they will contact you.

Post Views: 5,214

Thanks a lot to my Patreon Supporters: Matt Braun, Roman Postanciuc, Tobias Zindl, G Prvulovic, Reinhold Dröge, Abernitzke, Frank Grimm, Sakib, Broeserl, António Pina, Sergey Agafyin, Андрей Бурмистров, Jake, GS, Lawton Shoemake, Jozo Leko, John Breland, Venkat Nandam, Jose Francisco, Douglas Tinkham, Kuchlong Kuchlong, Robert Blanch, Truels Wissneth, Mario Luoni, Friedrich Huber, lennonli, Pramod Tikare Muralidhara, Peter Ware, Daniel Hufschläger, Alessandro Pezzato, Bob Perry, Satish Vangipuram, Andi Ireland, Richard Ohnemus, Michael Dunsky, Leo Goodstadt, John Wiederhirn, Yacob Cohen-Arazi, Florian Tischler, Robin Furness, Michael Young, Holger Detering, Bernd Mühlhaus, Stephen Kelley, Kyle Dean, Tusar Palauri, Juan Dent, George Liao, Daniel Ceperley, Jon T Hess, Stephen Totten, Wolfgang Fütterer, Matthias Grün, Phillip Diekmann, Ben Atakora, Ann Shatoff, Rob North, Bhavith C Achar, Marco Parri Empoli, Philipp Lenk, Charles-Jianye Chen, Keith Jeffery, Matt Godbolt, and Honey Sukesan.

Thanks, in particular, to Jon Hess, Lakshman, Christian Wittenhorst, Sherhy Pyton, Dendi Suhubdy, Sudhakar Belagurusamy, Richard Sargeant, Rusty Fleming, John Nebel, Mipko, Alicja Kaminska, Slavko Radman, and David Poole.

My special thanks to Embarcadero
My special thanks to PVS-Studio
My special thanks to Tipi.build
My special thanks to Take Up Code
My special thanks to SHAVEDYAKS