public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jlame646 at gmail dot com" <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 06:14:41 +0000	[thread overview]
Message-ID: <bug-107126-4-Ut6srpiXFg@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 #5 from Jason Liam <jlame646 at gmail dot com> ---
(In reply to Jakub Jelinek from comment #4)
> (In reply to Jason Liam from comment #2)
> > Second, i'm already aware that this is rejected by gcc with c++20 as i
> > provided a demo link https://godbolt.org/z/TYjEzss6q at the first line of my
> > bug report.
> 
> One thing is to know that some versions of g++ do that, but the above
> provides details on what change actually changed the behavior, which is
> useful information for any further changes.
> Then it is https://cplusplus.github.io/CWG/issues/1435.html which we perhaps
> don't implement or don't implement fully.

Note that the program shown in this bug is ill-formed in all c++ versions
including c++17. That is, it is different from
https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#2237 because that
cwg defect report only talks about declarations that are in the member
specification of the class and not in the namespace scope.

This means that the program shown in that cwg defect report is ill-formed only
from c++20 and onwards. But the program shown in my bug is ill-formed with all
modern c++ version including c++17. So this is a different bug.

  parent reply	other threads:[~2022-10-03  6:14 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 [this message]
2022-10-03  6:40 ` jlame646 at gmail dot com
2022-10-03  9:51 ` redi at gcc dot gnu.org
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-Ut6srpiXFg@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: link
Be 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).