public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/112942] swap(variant&, variant&) is incorrectly marked as deleted
Date: Sun, 10 Dec 2023 01:04:50 +0000 [thread overview]
Message-ID: <bug-112942-4-fhKcTNm4s4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112942-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112942
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Artem Koton from comment #3)
> (In reply to Andrew Pinski from comment #1)
> > https://wg21.cmeerw.net/lwg/issue2749
>
> Could you elaborate? I understand that this issue discusses the constraints
> in question but a failure to meet them should still result in the function
> just being excluded from overload resolution. The program should not be
> ill-formed.
Just giving background information of the wording changes to C++17 on
std::variant and std::swap here and about the testcase you pointed to and about
when it was added specifcially while changing for that defect report.
next prev parent reply other threads:[~2023-12-10 1:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 0:28 [Bug libstdc++/112942] New: " kotonartem at protonmail dot com
2023-12-10 0:30 ` [Bug libstdc++/112942] " pinskia at gcc dot gnu.org
2023-12-10 0:35 ` pinskia at gcc dot gnu.org
2023-12-10 0:54 ` kotonartem at protonmail dot com
2023-12-10 1:04 ` pinskia at gcc dot gnu.org [this message]
2023-12-10 12:36 ` [Bug libstdc++/112942] [LWG2766] " redi at gcc dot gnu.org
2023-12-10 12:37 ` redi 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-112942-4-fhKcTNm4s4@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).