https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65470
--- Comment #8 from aral at gmx dot de ---
I agree that updating the documentation exceeds the responsibility of this bug
reporting system, and if the behavior is intended, it is not a bug. The
severity was referring to the case had the behavior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65470
--- Comment #4 from aral at gmx dot de ---
Addition: after you referred to the properties of match_results, I had a look
at
http://en.cppreference.com/w/cpp/regex/match_results
which has a clearer wording. However, I still think this clear
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65470
--- Comment #3 from aral at gmx dot de ---
I don't argue that it might be a misunderstanding of the user, hence my
suggestion 1) - however, I disagree with your wording "clearly documented" as
far as
(a) http://en.cppreference.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65470
--- Comment #1 from aral at gmx dot de ---
AFAICT the same bug is applicable to the regex_match function. Sorry for the
copy & paste error in the very last comment.
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: aral at gmx dot de
Created attachment 35063
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35063&action=edit
minimal bug example - compile with g++ -std=c++11 regexbug.cpp -o r
