.. likewise.
On 04/10/18 12:32, Paolo Carlini wrote:
Hi,
yesterday I didn't notice that we have a separate bug for a similar
issue affecting cp_parser_compound_requirement. Tested x86_64-linux.
Thanks, Paolo.
PS: while working on these issues, I noticed that somewhere else in
the concepts parsing bits we check the return value of
cp_parser_require and, in case, immediately return error_mark_node.
That doesn't seem a good idea - and isn't what we do for all the other
cp_parser_require semicolon calls - because it normally degrades error
recovery when the only bug in the code is the missing semicolon. I
mean to further look into that...
https://gcc.gnu.org/ml/gcc-patches/2018-10/msg00239.html
Thanks! Paolo.
