public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/80711] warn on non-const accessor member functions Date: Sun, 10 May 2020 08:52:06 +0000 [thread overview] Message-ID: <bug-80711-4-om5glh0FzX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-80711-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80711 --- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> --- A first approximation that is implemented in the wrong part of the compiler, using the wrong logic, giving the wrong answers, is not a step in the right direction because it would need to be completely redone. Might as well just start the right version and skip that first approximation.
next prev parent reply other threads:[~2020-05-10 8:52 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-80711-4@http.gcc.gnu.org/bugzilla/> 2020-05-08 15:57 ` msebor at gcc dot gnu.org 2020-05-08 17:55 ` dcb314 at hotmail dot com 2020-05-09 0:05 ` msebor at gcc dot gnu.org 2020-05-09 8:25 ` redi at gcc dot gnu.org 2020-05-09 8:36 ` dcb314 at hotmail dot com 2020-05-09 18:55 ` redi at gcc dot gnu.org 2020-05-09 20:27 ` dcb314 at hotmail dot com 2020-05-10 8:42 ` redi at gcc dot gnu.org 2020-05-10 8:52 ` redi at gcc dot gnu.org [this message] 2020-05-10 9:45 ` dcb314 at hotmail 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-80711-4-om5glh0FzX@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).