https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109740
--- Comment #2 from Paul Smith <psmith at gnu dot org> --- What I'm trying to say is that it's not useful (to me) for GCC to warn about code that I could maybe write in the future but didn't actually write, and which if I did write it would generate a compiler error anyway, rather than "doing the wrong thing". On the other hand, it's very useful for GCC to warn me about situations where I could be actually getting an unexpected result, without a compiler error. For example if the parent method takes an int and the child method takes a char, then I might call B.foo(10) expecting to get the parent method but actually the child method will be invoked. That kind of warning is very helpful. So, it would be nice to have a way to warn about things that might miscompile silently in unexpected ways, without also warning about things that can't possibly miscompile in unexpected ways. I did read the description in the docs, and the suggestion of adding using A::foo to the child class, but that inherits all the parent class's virtual methods into the child class which I don't want to do in all cases.
