diff options
| author | Jason Merrill <jason@redhat.com> | 2022-11-21 16:05:23 -0500 |
|---|---|---|
| committer | Jason Merrill <jason@redhat.com> | 2022-11-28 15:50:43 -0500 |
| commit | 297bbe2d0dea083344e66e3e72fa791b5855a3de (patch) | |
| tree | 98adfa0a2c6e6e5c9643130082262b15678ea674 | |
| parent | 47d81b1b89d615cea27307c713a4afe591e1cd2d (diff) | |
| download | gcc-297bbe2d0dea083344e66e3e72fa791b5855a3de.zip gcc-297bbe2d0dea083344e66e3e72fa791b5855a3de.tar.gz gcc-297bbe2d0dea083344e66e3e72fa791b5855a3de.tar.bz2 | |
c++: be more strict about 'concept bool'
Some clang folks mailed me asking about being less permissive about
'concept bool', so let's bump it up from pedwarn to permerror.
gcc/cp/ChangeLog:
* parser.cc (cp_parser_decl_specifier_seq): Change 'concept bool'
diagnostic from pedwarn to permerror.
| -rw-r--r-- | gcc/cp/parser.cc | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/gcc/cp/parser.cc b/gcc/cp/parser.cc index aec625e..82459b7 100644 --- a/gcc/cp/parser.cc +++ b/gcc/cp/parser.cc @@ -15831,11 +15831,11 @@ cp_parser_decl_specifier_seq (cp_parser* parser, { cp_token *next = cp_lexer_peek_token (parser->lexer); if (next->keyword == RID_BOOL) - pedwarn (next->location, 0, "the %<bool%> keyword is not " - "allowed in a C++20 concept definition"); + permerror (next->location, "the %<bool%> keyword is not " + "allowed in a C++20 concept definition"); else - pedwarn (token->location, 0, "C++20 concept definition syntax " - "is %<concept <name> = <expr>%>"); + error_at (token->location, "C++20 concept definition syntax " + "is %<concept <name> = <expr>%>"); } /* In C++20 a concept definition is just 'concept name = expr;' |