By Adrien Hamelin | Mar 27, 2020 01:22 PM | Tags: c++20
They will change a lot of things.
C++20: Coroutines - A First Overview
by Rainer Grimm
From the article:
C++20 provides four features that change the way we think about and write modern C++: concepts, the ranges library, coroutines, and modules. I already wrote a few posts to concepts and the ranges library. Let's have a closer look at coroutines...
By Adrien Hamelin | Mar 27, 2020 01:19 PM | Tags: community
Lots of things happened.
Trip report: February 2020 ISO C++ committee meeting, Prague
by Timur Doumler
From the article:
If you’re wondering why I didn’t write up a trip report for the November 2019 Belfast meeting – it’s because I gave that report live on CppCast instead. So check it out if you want to hear what happened at that meeting!
By DaPi | Mar 27, 2020 01:02 PM | Tags: advanced
Friendship and its correlation with ADL and templates.
by Dawid Pilarski
About the article:
About the friend functions, how they work with Argument Dependent Lookup and templates.
By Adrien Hamelin | Mar 17, 2020 01:05 PM | Tags: c++20
The series continue.
C++20: Python's map Function
by Rainer Grimm
From the article:
Today, I finish my experiment writing beloved Python functions in C++. So far, I implemented the Python functions filter, range, and xrange. Today, I have a closer look at the map function and combine the functions map and filter into one function...
By Adrien Hamelin | Mar 17, 2020 01:02 PM | Tags: c++20
The series continue.
C++20: Pythons range Function, the Second
by Rainer Grimm
From the article:
In my last post C++20: Pythonic with the Ranges Library, I started my experiment to implement the beloved Python functions range and filter in C++. Due to two very interesting comments to my last post, I revisit the function range.
By Adrien Hamelin | Mar 17, 2020 12:58 PM | Tags: None
C++ becoming easier to use?
C++20: Pythonic with the Ranges Library
by Rainer Grimm
From the article:
Today, I start an experiment. I want to implement beloved functions in Python in C++ using the ranges library. I'm curious about how it goes...
By Adrien Hamelin | Mar 3, 2020 02:45 PM | Tags: c++20
Learn more about the new features.
C++20: Functional Patterns with the Ranges Library
by Rainer Grimm
From the article:
My last post C++20: The Ranges Library, gave you the first impression of the ranges library. Today's post is about functional patterns: function composition and lazy evaluation. They become first-class citizens in C++20...
By ctr_peach | Mar 2, 2020 07:17 AM | Tags: c++20
Using user-defined literal classes as non-type template parameters in C++20.
Literal classes as non-type template parameters in C++20
From the article:
/** * Prints whether or not a value was provided for "maybe" WITHOUT branching*/ template<OptionalInt maybe> void Print() { if constexpr(maybe.has_value) { std::cout << "Value is: " << maybe.value << std::endl; } else { std::cout << "No value." << std::endl; } }
[intermediate][C++20]
By triangles | Feb 27, 2020 11:25 AM | Tags: None
Discovering one of the pillars of C++ generic programming.
A quick primer on type traits in modern C++
by Internal Pointers
From the article:
Type traits are a clever technique used in C++ template metaprogramming that gives you the ability to inspect and transform the properties of types.
By stephanakib | Feb 26, 2020 05:31 AM | Tags: None
In this excerpt from Large-Scale C++ Volume I: Process and Architecture, John Lakos presents how to organize and package component-based software in a uniform (domain-independent) manner. This chapter also provides the fundamental C++ design rules that govern how to develop modular software hierarchically in terms of components, packages, and package groups.
C++ Packaging and Design Rules
by John Lakos
From the article:
The way in which software is organized governs the degree to which we can leverage that software to solve current and new business problems quickly and effectively. By design, much of the code that we write for use by applications will reside in sharable libraries and not directly in any one application. Our goal, therefore, is to provide some top-level organizational structure that allows us to partition our software into discrete physical units so as to facilitate finding, understanding, and potentially reusing available software solutions.