Mar 23-25, Bochum, Ger
Apr 19-22, Online and Bristol, UK
Apr 27, Madrid, Spain
June 10, Rome, Italy
June 27-30, Folkestone, UK
By Adrien Hamelin | Mar 17, 2022 01:55 PM | Tags: intermediate
The series continue.
Dynamic and Static Polymorphism
by Rainer Grimm
From the article:
Polymorphism is the property that different types support the same interface. In C++, we distinguish between dynamic polymorphism and static polymorphism...
By Adrien Hamelin | Mar 17, 2022 01:52 PM | Tags: intermediate
What's your preferred way?
Ways to Refactor Toggle/Boolean Parameters in C++
by Bartlomiej Filipek
From the article:
Boolean parameters in a function might be misleading and decrease its readability. If you have a poorly named function like:
DoImportantStuff(true, false, true, false);As you can imagine, it’s not clear what all those parameters mean? What’s the first true? What does the last false mean? Can we improve code in such cases?
Let’s have a look at possible improvements...
By Adrien Hamelin | Feb 25, 2022 12:05 PM | Tags: intermediate c++20
You don't know them yet?
The 114 standard C++ algorithms. Introduction
by Šimon Tóth
From the article:
Welcome to a new series on C++ standard algorithms. Standard algorithms offer safe and optimized building blocks that can replace a surprising amount of user code...
By Adrien Hamelin | Feb 23, 2022 02:48 PM | Tags: intermediate
Are you familiar with it?
SFINAE: Substitution Failure is not an Error | Top-Up C++ [C++ #02]
by WolfSound
Summary of the video:
In this video, we are presenting SFINAE: Substitution Failure is not an Error, a feature or a characteristic of C++ related to templates. “Substitution failure is not an error” means that if the compiler fails to specialize a template with a given template argument list, it does not issue an error. It does when it cannot find any suitable function/class to be called/instantiated (either due to a lack of suitably declared functions/classes or an error during instantiation).
By Adrien Hamelin | Jan 26, 2022 09:45 AM | Tags: intermediate
Which way do you prefer?
Fixing the crash that seems to be on a std::move operation
by Raymond Chen
From the article:
Last time, we looked at a crash that was root-caused to an order of evaluation bug if compiled as C++14. One solution to the problem is to switch to C++17 mode, but presumably the customer isn’t willing to make that drastic a change to their product yet. Maybe there’s something we can do that is less disruptive...
By Adrien Hamelin | Dec 20, 2021 03:57 PM | Tags: intermediate
The series continue.
The Type-Traits Library: Correctness
by Rainer Grimm
From the article:
The two main goals of the type-traits library are very convincing: correctness and optimization. Today, I write about correctness...
By Adrien Hamelin | Nov 30, 2021 02:02 PM | Tags: intermediate c++11
The series continue.
The Type-Traits Library: Type Checks
by Rainer Grimm
From the article:
The type-traits library is part of C++11 and supports type checks, type comparisons, and type modifications at compile-time. The library has more than 100 functions but grows with each new C++ standard release. Today, I present the type checks...
By Adrien Hamelin | Nov 28, 2021 11:56 PM | Tags: intermediate
Did you ever use that?
Design Patterns VS Design Principles: Template Method
by Jonathan Boccara
From the article:
In today’s episode of “Design Pattens VS Design Principles” series, we relate the Template Method design patterns to more general design principles. We’re showing how it relates to the Polymorphism design principle...
By Adrien Hamelin | Nov 28, 2021 11:54 PM | Tags: intermediate
Will you try?
Template Metaprogramming - Hybrid Programming
by Rainer Grimm
From the article:
First of all, hybrid programming is not an official term. I created it to emphasize a very interesting aspect of templates. The difference between function arguments and template arguments...
By Adrien Hamelin | Nov 5, 2021 02:44 PM | Tags: intermediate
Are you interested?
Strong Types for Safe Indexing in Collections – Part 2
by Jonathan Boccara
From the article:
In the previous article on strong types, we set out to find how to use strong types for safe indexing in collections.
More precisely, if we have two vectors with two indices to access them, how can we use strong types to make sure we use the right index for the right vector, and that we don’t swap them by mistake?