concepts

Let me conclude my series to concepts with this meta-post. Are concepts an evolution or a revolution in C++? The answer to this question bothered me quite a time.

When you want to define a concrete type that works well in the C++ ecosystem, you should define a type that "behaves link an int". Formally, your concrete type should be a regular type. In this post, I define the concepts Regular and SemiRegular.

In my last post, I defined the concept Equal. Now, I go one step further and use the concept Equal to define the concept Ordering.

With this post, I start my last very exciting topic to concepts: define your concepts. Consequentially, I answer the questions I opened in previous posts.

C++20 has many predefined concepts. Consequentially, before you define your concept, you should know the existing ones. This post gives you an overview of the predefined concepts. To get the general idea of concepts, read my previous posts. 

The Template Introduction from the Concepts TS is a new way to use concepts. This syntactic variant is not included in the Concepts Draft and, therefore, in the C++20 standard. But, I don't know what the farther away future brings.

Today, my post is not about something new to concepts. It's about syntactic sugar. I write about abbreviated function templates. What? Abbreviated functions templates allow a sweet way to define templates.

Today, I have a simple answer to a challenging question: Where can I use my concept? Concepts can be used where auto is usable.

In my last post C++20: Two Extremes and the Rescue with Concepts, I gave the first motivation for concepts. Concepts put semantic constraints on template parameters. Today, I present different use-cases for concepts in a compact form.

I finished my overview of C++20 in the last post. Now, it's time to dive into the details. What can be a better starting point for our journey than concepts?