public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "de34 at live dot cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/113007] `std::variant` converting constructor and `operator=` compile while the C++ Standard says they must not
Date: Mon, 19 Feb 2024 10:13:18 +0000 [thread overview]
Message-ID: <bug-113007-4-WI9Qgse2UQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113007-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113007
Jiang An <de34 at live dot cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |de34 at live dot cn
--- Comment #8 from Jiang An <de34 at live dot cn> ---
(In reply to Pavel Novikov from comment #7)
> Now it's time to file a bug in MSVC's standard library.
This was by design. MSVC STL intendedly only enabled changes in P0608R3 since
C++20 (https://github.com/microsoft/STL/pull/1629#issuecomment-778895630).
But given the author of P0608R3 applied the changes to libc++ in C++17 mode, I
think it makes more sense to treat it as a DR.
I've opened this issue:
https://github.com/microsoft/STL/issues/4412
prev parent reply other threads:[~2024-02-19 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 21:11 [Bug libstdc++/113007] New: " paul.skeptic at yandex dot ru
2023-12-13 21:15 ` [Bug libstdc++/113007] " pinskia at gcc dot gnu.org
2023-12-14 1:03 ` redi at gcc dot gnu.org
2023-12-14 1:06 ` redi at gcc dot gnu.org
2023-12-14 10:58 ` paul.skeptic at yandex dot ru
2023-12-14 14:18 ` redi at gcc dot gnu.org
2023-12-14 14:20 ` redi at gcc dot gnu.org
2023-12-14 15:44 ` paul.skeptic at yandex dot ru
2024-02-19 10:13 ` de34 at live dot cn [this message]
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-113007-4-WI9Qgse2UQ@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).