We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The core clauses mention library concepts in some examples.
It is our habit to prefix names from the standard library with std:: if they appear in the core language clauses, to highlight their provenance.
std::
I'd like to have a nod that we'll be doing the same for concept names from the standard library.
The text was updated successfully, but these errors were encountered:
Can you provide some examples?
Sorry, something went wrong.
Good: [over.match.class.deduct] p6
template<std::integral W> using B = A<W>;
Bad: [expr.prim.req] p3
template<typename T> concept R = requires (T i) { typename T::type; {*i} -> convertible_to<const typename T::type&>; };
(Since this is an example in the definition of requires-expression, readers might be tricked into thinking that convertible_to is a built-in thing.)
convertible_to
Editorial meeting: Agreed, add std:: prefixes.
jensmaurer
Successfully merging a pull request may close this issue.
The core clauses mention library concepts in some examples.
It is our habit to prefix names from the standard library with
std::
if they appear in the core language clauses, to highlight their provenance.I'd like to have a nod that we'll be doing the same for concept names from the standard library.
The text was updated successfully, but these errors were encountered: