public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi 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: Mon, 25 Apr 2022 14:54:42 +0000 [thread overview] Message-ID: <bug-105375-4-xdtdKHBq8C@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 #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to raldone01 from comment #5) > Thank you for your reply. > What does that mean? As it says at the link in comment 4, "The following behavior-changing defect reports were applied retroactively to previously published C++ standards." > Are defect reports updates for older standards? Yes. > Is it meant to be available at some point in c++17? Yes.
next prev parent reply other threads:[~2022-04-25 14:54 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 [this message] 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 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-xdtdKHBq8C@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).