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++/65092] Container adaptors missing allocator-extended constructors Date: Fri, 11 Sep 2015 09:52:00 -0000 [thread overview] Message-ID: <bug-65092-4-3xYEtJGgZm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65092-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65092 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- Author: redi Date: Fri Sep 11 09:51:29 2015 New Revision: 227680 URL: https://gcc.gnu.org/viewcvs?rev=227680&root=gcc&view=rev Log: Allocator-extended constructors for container adaptors. PR libstdc++/65092 * include/bits/stl_queue.h (queue, priority_queue): Add allocator-extended constructors. * include/bits/stl_stack.h (stack): Likewise. * testsuite/23_containers/priority_queue/requirements/ uses_allocator.cc: Test allocator-extended constructors. * testsuite/23_containers/queue/requirements/uses_allocator.cc: Likewise. * testsuite/23_containers/stack/requirements/uses_allocator.cc: Likewise. Modified: trunk/libstdc++-v3/ChangeLog trunk/libstdc++-v3/include/bits/stl_queue.h trunk/libstdc++-v3/include/bits/stl_stack.h trunk/libstdc++-v3/testsuite/23_containers/priority_queue/requirements/uses_allocator.cc trunk/libstdc++-v3/testsuite/23_containers/queue/requirements/uses_allocator.cc trunk/libstdc++-v3/testsuite/23_containers/stack/requirements/uses_allocator.cc
next prev parent reply other threads:[~2015-09-11 9:52 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-17 18:06 [Bug libstdc++/65092] New: " rs2740 at gmail dot com 2015-02-18 12:06 ` [Bug libstdc++/65092] " redi at gcc dot gnu.org 2015-09-11 9:52 ` redi at gcc dot gnu.org [this message] 2015-09-11 9:52 ` 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-65092-4-3xYEtJGgZm@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).