public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/94562] C++20: std::shared_ptr<int>{} <=> nullptr ill-formed
Date: Tue, 14 Apr 2020 20:55:09 +0000	[thread overview]
Message-ID: <bug-94562-4-CUMSe3RyyD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94562-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94562

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:f5fa62ed19a1c85cda920bbe05eb075d8f2a0b42

commit r10-7725-gf5fa62ed19a1c85cda920bbe05eb075d8f2a0b42
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Apr 14 21:54:55 2020 +0100

    libstdc++: Add comparison operators to std::shared_ptr (PR 94562)

    This also implements the proposed resolution to LWG issue 3247, so that
    the ill-formed <=> expression with nullptr is not used.

            PR libstdc++/94562
            * include/bits/shared_ptr.h (operator<=>): Define for C++20.
            * include/bits/shared_ptr_base.h (operator<=>): Likewise.
            * include/bits/unique_ptr.h (operator<=>): Add inline specifier.
            * testsuite/20_util/shared_ptr/comparison/cmp_c++20.cc: New test.
            * testsuite/20_util/shared_ptr/comparison/less.cc: Do not expect
            std::less<A*> to be used when comparing std::shared_ptr<A> objects
in
            C++20.

  parent reply	other threads:[~2020-04-14 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-11 19:04 [Bug libstdc++/94562] New: " daniel.kruegler at googlemail dot com
2020-04-11 19:05 ` [Bug libstdc++/94562] " redi at gcc dot gnu.org
2020-04-14 20:55 ` cvs-commit at gcc dot gnu.org [this message]
2020-04-14 22:51 ` 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-94562-4-CUMSe3RyyD@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).