Behavior of concepts with a default template parameter
Consider this concept, which has a default template parameter.
Can I declare a requirement-parameter as an r-value?
I’ve got a thread-queue with a generic callback that takes the queue elements. This is the minimally reduced code:
Best concept to check that all types in a parameter pack are unique
I am trying to find the most efficient and clear way to define a C++20 concept to check that all types in a parameter pack are unique.
concept implicitly_convertible_to
I know about std::convertible_to<From, To>
but it includes also explicit conversions (static/const).
How to avoid template constraint failure in the non-selected type when using std::conditional?
I need to select between two types for a variable at compile time. One of these types have a concept requirement which is not always satisfied and that is when I want to select the other type. I am trying to achieve this with std::conditional_t, but both types to std::conditional are evaluated causing a template constraint failure.
How to create a recursive C++ concept with a parameter pack that is called recursively
Is there a way – and if yes, how – to create a C++ concept that includes a parameter pack for the checked type and is then called recursively, such that more matches yield a better match for overloading?
Define concept where a type is invocable with argument satisfying concept
Given the following concept