https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16168
--- Comment #11 from Eric Gallager <egallager at gcc dot gnu.org> --- (In reply to Oren Ben-Kiki from comment #10) > All good points, which you could say about many opened bugs. > > The `-Weffc++` flag is a useful tool to keep large code bases working, even > when written by less-than-guru C++ programmers. As someone tending a large > framework used by such developers, this specific bug "has non-trivial impact > on my code base", hence the original comment expressing the need for it to > be fixed. > I agree that an ideal -Weffc++ would be useful, however, the current implementation needs a lot of improvement to get there, which is why I opened a meta-bug for issues related to -Weffc++ (bug 81930) > I assume that the GCC maintainers keep an eye on the bug boards and fix bugs > depending on their impact on people's code. I hope this matched reality :-) I keep an eye on the bug boards, but I mostly just triage them and don't actually fix them... the people who do the actual fixing have their own criteria for which ones they decide to fix. Usually "impact on people's code" is judged more by stuff actually breaking (see the wrong-code and rejects-valid keywords) than by... well, whatever criteria might be applicable here. > > I suppose using the word "annoying", while concise, might have convey > additional unintentional connotations; if so, consider this a clarification > of the original intent.
