https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90880
Patrick Palka changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90880
--- Comment #5 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:4f6c1ca287d2c64856ef67fa50bc462633d5b8cf
commit r11-21-g4f6c1ca287d2c64856ef67fa50bc462633d5b8cf
Author: Patrick Palka
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90880
Patrick Palka changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90880
--- Comment #4 from Jonathan Wakely ---
(In reply to Federico Kircheis from comment #3)
> Sorry if linking to external bug trackers in comments is bad practice, but I
> did not saw any rule about it.
There's no rule against it, it's useful.
> S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90880
--- Comment #3 from Federico Kircheis ---
(In reply to Jonathan Wakely from comment #2)
> (In reply to Federico Kircheis from comment #1)
> > After researching a little bit more, I've convinced myself that
> > `status::value` should be false, as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90880
Jonathan Wakely changed:
What|Removed |Added
Keywords||rejects-valid
Status|UNCON
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90880
--- Comment #1 from Federico Kircheis ---
After researching a little bit more, I've convinced myself that
`status::value` should be false, as `decltype` has no special rules for
accessing private data, thus clang is correct.
If someone could con
