[Bug c++/57239] cannot handle inner/nested class templates with non-type parameter packs that were declared in the outer/containing class

[redi at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57239

--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to etherice from comment #10)
> Isn't it defeating the purpose of having a 'status' field if it's not being
> used?

What makes you think it isn't used?  Paolo is saying that the difference
between UNCONFIRMED and NEW is often irrelevant for the submitter's purposes,
that doesn't mean the entire field isn't used. The ASSIGNED and RESOLVED values
are obviously not the same as UNCONFIRMED/NEW.

> It seems especially important for the situation you mentioned -- for
> the "hard bugs" that take longer to fix, an *initial* status update informs
> the submitter that the bug report has been reviewed and is on the dev team's
> radar. Otherwise, it's like the report is never even acknowledge until it's
> actually fixed, and I imagine most submitters will seek *some* kind of
> status update eventually.

But there is no "dev team" so there's no radar for it to meaningfully be on. 
That's not how GCC works.  Confirming the bug means at least one person agrees
it's a real bug, and noone else has disagreed strongly enough to say it's
INVALID, it doesn't mean it's on anyone's TODO list or a fix is in progress.