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++/103091] [DR 2256] Can't jump into scope of a variable with a nontrivial destructor in C++20
Date: Fri, 05 Nov 2021 08:07:25 +0000 [thread overview]
Message-ID: <bug-103091-4-099VGof9sc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103091-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103091
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> which is consider CD5.
That's just a detail of which draft of was included in, which doesn't mean
much. More relevant is that it was approved as a DR so it applies to C++17 (and
earlier) too.
next prev parent reply other threads:[~2021-11-05 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 6:29 [Bug c++/103091] New: " josephcsible at gmail dot com
2021-11-05 6:51 ` [Bug c++/103091] [DR 2256] " pinskia at gcc dot gnu.org
2021-11-05 6:52 ` pinskia at gcc dot gnu.org
2021-11-05 8:07 ` redi at gcc dot gnu.org [this message]
2023-05-07 16:09 ` cvs-commit at gcc dot gnu.org
2023-05-07 16:10 ` ppalka 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-103091-4-099VGof9sc@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).