public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "psmith at gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109740] -Woverloaded-virtual is too aggressive Date: Thu, 04 May 2023 17:45:29 +0000 [thread overview] Message-ID: <bug-109740-4-v9UQVm8Vjf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109740-4@http.gcc.gnu.org/bugzilla/> 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.
next prev parent reply other threads:[~2023-05-04 17:45 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-04 16:40 [Bug c++/109740] New: " psmith at gnu dot org 2023-05-04 16:46 ` [Bug c++/109740] " pinskia at gcc dot gnu.org 2023-05-04 17:45 ` psmith at gnu dot org [this message] 2023-11-01 18:04 ` emerg.reanimator at gmail dot com 2023-11-01 18:56 ` emerg.reanimator at gmail dot com 2023-11-02 20:52 ` emerg.reanimator at gmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-109740-4-v9UQVm8Vjf@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).