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++/91456] std::function and std::is_invocable_r do not understand guaranteed elision
Date: Tue, 16 May 2023 12:50:42 +0000	[thread overview]
Message-ID: <bug-91456-4-3Vck4xDOw4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91456-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:5c02a8eca7bcbe0ee021eddd5f764e8bfcb13b03

commit r11-10775-g5c02a8eca7bcbe0ee021eddd5f764e8bfcb13b03
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Sep 23 13:28:37 2022 +0100

    libstdc++: Fix std::is_nothrow_invocable_r for uncopyable prvalues
[PR91456]

    This is the last missing piece of PR 91456.

    This also removes the only use of the C++11 version of
    std::is_nothrow_invocable.

    libstdc++-v3/ChangeLog:

            PR libstdc++/91456
            * include/std/type_traits (__is_nothrow_invocable): Remove.
            (__is_invocable_impl::__nothrow_type): New member type which
            checks if the conversion can throw.
            (__is_nt_invocable_impl): Replace class template with alias
            template to __is_nt_invocable_impl::__nothrow_type.
            * testsuite/20_util/is_nothrow_invocable/91456.cc: New test.
            * testsuite/20_util/is_nothrow_convertible/value.cc: Remove
            macro used by value_ext.cc test.
            * testsuite/20_util/is_nothrow_convertible/value_ext.cc: Remove
            test for non-standard __is_nothrow_invocable trait.

    (cherry picked from commit 71c828f84572d933979468baf2cf744180258ee4)

      parent reply	other threads:[~2023-05-16 12:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-91456-4@http.gcc.gnu.org/bugzilla/>
2022-05-09 16:29 ` hewillk at gmail dot com
2022-09-21 14:03 ` cvs-commit at gcc dot gnu.org
2022-09-24  0:07 ` cvs-commit at gcc dot gnu.org
2022-09-24  9:38 ` redi at gcc dot gnu.org
2022-11-24 16:36 ` cvs-commit at gcc dot gnu.org
2023-05-16 12:50 ` cvs-commit at gcc dot gnu.org [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-91456-4-3Vck4xDOw4@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).