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++/105375] std::packaged_task has no deduction guide. Date: Tue, 26 Apr 2022 12:31:00 +0000 [thread overview] Message-ID: <bug-105375-4-bYdR0lbI6W@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105375-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105375 --- Comment #9 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:eb6f6f638a547f0330cc7940c5389039b59e4e76 commit r11-9936-geb6f6f638a547f0330cc7940c5389039b59e4e76 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Apr 25 14:22:41 2022 +0100 libstdc++: Add deduction guides for std::packaged_task [PR105375] This change was LWG 3117. The test is copied from 20_util/function/cons/deduction.cc libstdc++-v3/ChangeLog: PR libstdc++/105375 * include/std/future (packaged_task): Add deduction guides. * testsuite/30_threads/packaged_task/cons/deduction.cc: New test. (cherry picked from commit a5cee0480c10bafa8ed65d49e5cedca23d98d7b7)
next prev parent reply other threads:[~2022-04-26 12:31 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-25 12:49 [Bug libstdc++/105375] New: " raldone01 at gmail dot com 2022-04-25 12:49 ` [Bug libstdc++/105375] " raldone01 at gmail dot com 2022-04-25 12:51 ` raldone01 at gmail dot com 2022-04-25 13:12 ` redi at gcc dot gnu.org 2022-04-25 13:21 ` redi at gcc dot gnu.org 2022-04-25 13:51 ` raldone01 at gmail dot com 2022-04-25 14:54 ` redi at gcc dot gnu.org 2022-04-25 16:05 ` cvs-commit at gcc dot gnu.org 2022-04-25 16:25 ` redi at gcc dot gnu.org 2022-04-26 12:31 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-26 12:31 ` 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-105375-4-bYdR0lbI6W@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: linkBe 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).