C++ Stories in March

Have a look at a short summary of the best articles from March 2021 from the C++ community.

Reminder: I publish new articles at the converted website cppstories.com.

C++ Lambda Story in Print @CppStories

 See a new article @CppStories with details about the latest updates for C++ Lambda Story. Now you can get the book in print!

C++ Lambda Story in Print

First Year At Patreon

A bit more than a year ago I started my Patreon page! It was an experiment, and I’m pleased that it has a lot of benefits. In this short blog post, I’d like to make a small summary, share my thoughts and plans for the next year.

You can also learn how to get “one year” of my extra C++ content!

 

C++ at the end of 2020! @CppStories

 See my summary article!

Available @C++Stories:

C++ At the end of 2020

One Trick with Private Names and Function Templates @C++Stories

Have a look at a new article @C++Stories! 

This time I have one trick with nested types, private names and function templates. 

See her:

One Trick with Private Names and Function Templates

 

 

C++ at the End of 2020, Survey

It’s almost the end of the year!

I prepared a quick survey, so we can learn about our experience with the language.

(The survey has ended, thanks for your votes! Stay tuned for a summary blog post :))

Why Not a Functor and Lambda Story Updates @CppStories

I’m happy to announce a new update to my book on lambda expressions! A few pages more, and what’s important is that I heavily improved the consistency and some wording. All of that, thanks to valuable input from my readers and C++ experts. And today we’ll also have a look at one wording case - what’s a functor? And is a lambda a functor?

 See @CppStories:

Why Not a Functor and Lambda Story Updates @CppStories

 

New post at C++ Stories: Under the Covers of C++ Lambdas

See a new blog post at C++ Stories!

This time it's a guest post by Andreas Fertig who explains the problems of translating lambda syntax into the closure type.

See here:

Under the Covers of C++ Lambdas: Captures, Captures, Captures @C++Stories

 

The First New Article on C++ Stories!

Since more than a year I've been developing a "shadow" website called C++ Stories that will eventually take please of this blog. The site is live and most of my articles are also available there.

Today I'm happy to invite you to a fresh new post available only at cppstories.com!

Have a look:

How to Share Code with Const and Non-Const Functions in C++

Runtime Polymorphism with std::variant and std::visit

Runtime polymorphism usually connects with v-tables and virtual functions. However, in this blog post, I’ll show you a modern C++ technique that leverages std::variant and std::visit. This C++17 technique might offer not only better performance and value semantics but also interesting design patterns.

C++20 Ranges, Projections, std::invoke and if constexpr

Continuing the topic from last week, let’s dive into the topic of std::invoke. This helper template function helps with uniform syntax call for various callable object types and can greatly reduce the complexity of our generic code.

17 Smaller but Handy C++17 Features

When you see an article about new C++ features, most of the time you’ll have a description of major elements. Looking at C++17, there are a lot of posts (including articles from this blog) about structured bindings, filesystem, parallel algorithms, if constexpr, std::optional, std::variant… and other prominent C++17 additions.

But how about some smaller parts? Library or language improvements that didn’t require decades to standardise or violent “battles” at the ISO meetings.

In this article, I’ll show you 17 (plus a few extra!) smaller C++17 things that will improve your code.

Increased Complexity of C++20 Range Algorithms Declarations - Is It Worth?

With the addition of Ranges and Concepts in C++20, our good old algorithm interfaces got super long “rangified” versions. For example, copy is now 4 lines long… and it’s just the declaration!

template <ranges::input_range R, std::weakly_incrementable O>
requires std::indirectly_copyable<ranges::iterator_t<R>, O>
constexpr ranges::copy_result<ranges::borrowed_iterator_t<R>, O>
copy(R&& r, O result);

How to decipher such a long declaration? What benefits do we get instead? Is it worth it? Let’s find out.

How To Stay Sane with Modern C++

C++ grows very fast! For example, the number of pages of the C++ standard went from 879 pages for C++98/03 to 1834 for C++20! Nearly 1000 pages! What’s more, with each revision of C++, we get several dozens of new features. Have a look at my blog post with all C++17 features, it shows 48 items, and my C++20 reference card lists 47 elements!

Do you need to learn all of that stuff to write good code?

How to stay sane in the C++ world today?