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: Wed, 21 Sep 2022 14:03:03 +0000	[thread overview]
Message-ID: <bug-91456-4-v7TarzOz6A@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 #7 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:5814816641389dd76153aae63e8ccb67a1a9a321

commit r13-2764-g5814816641389dd76153aae63e8ccb67a1a9a321
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Wed Sep 21 14:59:18 2022 +0100

    libstdc++: Fix accidental duplicate test [PR91456]

    It looks like I committed the testcase for std::function twice, instead
    of one for std::function and one for std::is_invocable_r. This replaces
    the is_invocable_r one with the example from the PR.

    libstdc++-v3/ChangeLog:

            PR libstdc++/91456
            * testsuite/20_util/function/91456.cc: Add comment with PR
            number.
            * testsuite/20_util/is_invocable/91456.cc: Likewise. Replace
            std::function checks with std::is_invocable_r checks.

  parent reply	other threads:[~2022-09-21 14:03 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 [this message]
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

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-v7TarzOz6A@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).