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++/49204] [C++0x] remaining issues in <future> Date: Fri, 23 Dec 2011 16:13:00 -0000 [thread overview] Message-ID: <bug-49204-4-GGZ5v7hGMa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49204-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49204 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-12-23 16:10:58 UTC --- Author: redi Date: Fri Dec 23 16:10:48 2011 New Revision: 182658 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=182658 Log: PR libstdc++/49204 * include/std/future (future_errc): Implement LWG 2056. Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/std/future
next prev parent reply other threads:[~2011-12-23 16:11 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-28 0:32 [Bug libstdc++/49204] New: " redi at gcc dot gnu.org 2011-05-28 0:41 ` [Bug libstdc++/49204] [C++0x] " redi at gcc dot gnu.org 2011-05-31 11:12 ` redi at gcc dot gnu.org 2011-05-31 14:00 ` redi at gcc dot gnu.org 2011-12-23 16:13 ` redi at gcc dot gnu.org [this message] 2011-12-30 13:12 ` redi at gcc dot gnu.org 2012-01-02 17:56 ` redi at gcc dot gnu.org 2012-02-01 0:20 ` redi at gcc dot gnu.org 2012-02-01 0:25 ` redi at gcc dot gnu.org 2012-02-03 9:22 ` redi at gcc dot gnu.org 2012-08-22 19:20 ` redi at gcc dot gnu.org 2013-03-22 14:42 ` jakub at gcc dot gnu.org 2013-03-23 15:02 ` redi at gcc dot gnu.org 2013-11-20 20:59 ` redi at gcc dot gnu.org 2013-11-20 21:02 ` redi at gcc dot gnu.org 2015-05-05 2:00 ` 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-49204-4-GGZ5v7hGMa@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).