C++20 concept syntax - what does the requires parameter variables mean?

user_358242 0
Viewed 825

Many articles give examples like this:

template<typename T>
concept Equal = requires(T a, T b) {
    { a == b } -> std::same_as<bool>;
};

Does it make any difference if I write:

template<typename T>
concept Equal = requires(T a) {
    { a == a } -> std::same_as<bool>;
};

If it doesn't, why was the syntax designed like this? Why do they ask me to declare these variables like a or b?

Why do I need multiple variables of the same type? And why do I even need variables?

template<typename T>
concept Equal = requires {
    { declval<const T&>() == declval<const T&>() }
        -> std::same_as<bool>;
};
c++-concepts c++20 c++
1 Answers

Why do they ask me to declare these variables like a or b? Why not even something like..

You aren't asked or required to use the variables. You are given the option because it's much more readable. There's little difference, as far as checking the constraints goes.

The reason the articles give examples like that one you cite, is because it's easier for humans to understand. The Equal concept is defined to read "given two hypothetical objects of this type, we can write a comparison expression with them, that results in a bool". That's it. You don't have to use this notation, you can write it with as much verbosity as you want.

But the old bit of wisdom about code still holds. Code is meant to be read far more than written, and not just in ways we foresee. When your concept is not satisfied in a context that results in a compiler error about a violated constraint, the compiler is likely to include the constraint in its error message. Which version of the concept is going to produce the easier-to-understand error message? My bet is on the one that uses helper variables.

user_8176430
Related