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 c++/106651] [C++23] P1169 - static operator()
Date: Tue, 27 Sep 2022 11:00:00 +0000 [thread overview]
Message-ID: <bug-106651-4-n5n3PiIJNx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106651-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106651
--- Comment #4 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:614e5696d730a65998ff5b0373f905795a758dd6
commit r13-2897-g614e5696d730a65998ff5b0373f905795a758dd6
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Tue Sep 27 11:25:51 2022 +0100
libstdc++: Adjust deduction guides for static operator() [PR106651]
Adjust the deduction guides for std::function and std::packaged_task to
work with static call operators. This finishes the implementation of
P1169R4 for C++23.
libstdc++-v3/ChangeLog:
PR c++/106651
* include/bits/std_function.h (__function_guide_t): New alias
template.
[__cpp_static_call_operator] (__function_guide_static_helper):
New class template.
(function): Use __function_guide_t in deduction guide.
* include/std/future (packaged_task): Use __function_guide_t in
deduction guide.
* testsuite/20_util/function/cons/deduction_c++23.cc: New test.
* testsuite/30_threads/packaged_task/cons/deduction_c++23.cc:
New test.
next prev parent reply other threads:[~2022-09-27 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 17:11 [Bug c++/106651] New: " mpolacek at gcc dot gnu.org
2022-09-12 17:46 ` [Bug c++/106651] " jakub at gcc dot gnu.org
2022-09-13 13:18 ` jakub at gcc dot gnu.org
2022-09-27 6:41 ` cvs-commit at gcc dot gnu.org
2022-09-27 11:00 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-27 11:00 ` redi at gcc dot gnu.org
2023-03-07 19:34 ` 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-106651-4-n5n3PiIJNx@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).