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++/113386] std::pair comparison operators should be transparent, but are not in libstdc++
Date: Sun, 14 Jan 2024 09:19:31 +0000 [thread overview]
Message-ID: <bug-113386-4-xQXcwcvBVJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113386-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113386
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jan Schultke from comment #0)
> Clang with -stdlib=libc++ compiles this, as does MSVC. Bug #90203 was
> incorrectly closed.
No PR 90203 was not closed incorrectly as that was what the C++ standard said
at the time (and even says still for C++20).
C++ LWG defect report 3865 added this to the standard for C++23:
https://cplusplus.github.io/LWG/lwg-defects.html#3865
GCC just does not implement that yet ...
next prev parent reply other threads:[~2024-01-14 9:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-14 9:01 [Bug libstdc++/113386] New: " janschultke at googlemail dot com
2024-01-14 9:03 ` [Bug libstdc++/113386] " janschultke at googlemail dot com
2024-01-14 9:19 ` pinskia at gcc dot gnu.org [this message]
2024-01-14 9:19 ` pinskia at gcc dot gnu.org
2024-01-14 9:24 ` [Bug libstdc++/113386] [C++23] " janschultke at googlemail dot com
2024-01-14 9:26 ` janschultke at googlemail dot com
2024-01-14 9:28 ` pinskia at gcc dot gnu.org
2024-01-14 9:55 ` janschultke at googlemail dot com
2024-01-14 12:55 ` redi at gcc dot gnu.org
2024-01-15 14:46 ` redi at gcc dot gnu.org
2024-01-29 20:29 ` redi at gcc dot gnu.org
2024-04-15 18:29 ` cvs-commit at gcc dot gnu.org
2024-04-15 18:33 ` 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-113386-4-xQXcwcvBVJ@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).