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++/107126] GCC accepts invalid out of class definition for destructor with C++17 Date: Mon, 03 Oct 2022 09:51:31 +0000 [thread overview] Message-ID: <bug-107126-4-Jp1uvMuIAY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107126-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107126 --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- https://wg21.link/cwg1435 introduced the wording that allows this (which can still be seen in the context for the [class.dtor] changes in CWG 2337): "in a declaration at namespace scope or in a friend declaration, the id-expression is nested-name-specifier ~class-name and the class-name names the same class as the nested-name-specifier." https://wg21.link/p1787r6 changed that to: "otherwise, the id-expression is nested-name-specifier ~class-name and the class-name is the injected-class-name of the class nominated by the nested-name-specifier." This seems like a breaking change that was not obvious from the revision history of the r5 paper: - Required destructor declarations to use the injected-class-name, avoiding name lookup - Simplified lookup for destructors - Specified that < begins a template argument list in a destructor name All compilers accept the program in C++17 mode, and I don't think it's at all clear that the code was always invalid in older standards, as you claim.
next prev parent reply other threads:[~2022-10-03 9:51 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-02 19:11 [Bug c++/107126] New: " jlame646 at gmail dot com 2022-10-02 19:41 ` [Bug c++/107126] " jakub at gcc dot gnu.org 2022-10-02 20:10 ` jlame646 at gmail dot com 2022-10-02 20:34 ` jlame646 at gmail dot com 2022-10-02 20:49 ` jakub at gcc dot gnu.org 2022-10-03 6:14 ` jlame646 at gmail dot com 2022-10-03 6:40 ` jlame646 at gmail dot com 2022-10-03 9:51 ` redi at gcc dot gnu.org [this message] 2022-10-03 14:29 ` [Bug c++/107126] -Wc++20-compat should complain about template-id in out of class definition for destructor jason at gcc dot gnu.org 2024-02-01 23:36 ` mpolacek at gcc dot gnu.org 2024-02-10 13:38 ` cvs-commit at gcc dot gnu.org 2024-02-10 13:45 ` mpolacek at gcc dot gnu.org
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-107126-4-Jp1uvMuIAY@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).