public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/44015] template parameters not documented Date: Wed, 02 May 2012 22:42:00 -0000 [thread overview] Message-ID: <bug-44015-4-HksHKQEmEY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-44015-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44015 Benjamin Kosnik <bkoz at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2012-05-02 CC| |bkoz at gcc dot gnu.org AssignedTo|unassigned at gcc dot |bkoz at gcc dot gnu.org |gnu.org | Target Milestone|--- |4.8.0 Ever Confirmed|0 |1 --- Comment #4 from Benjamin Kosnik <bkoz at gcc dot gnu.org> 2012-05-02 22:41:44 UTC --- I noticed this again recently, while mucking with std::unordered_set etc. The checked-in patch adds in the necessary markup for containers and io. It seems complete and consistent: string http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/a00428.html array http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/a00569.html basic_istream http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen/a00425.html etc. This is the way to write the markup for template parameters, and default arguments to them.
next prev parent reply other threads:[~2012-05-02 22:42 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44015-4@http.gcc.gnu.org/bugzilla/> 2012-05-02 22:26 ` bkoz at gcc dot gnu.org 2012-05-02 22:42 ` bkoz at gcc dot gnu.org [this message] 2013-03-22 14:43 ` jakub at gcc dot gnu.org 2013-05-31 10:57 ` jakub at gcc dot gnu.org 2013-10-16 9:51 ` jakub at gcc dot gnu.org 2015-06-22 14:26 ` rguenth at gcc dot gnu.org 2023-05-16 19:41 ` pinskia at gcc dot gnu.org 2010-05-06 17:36 [Bug libstdc++/44015] New: " giecrilj at stegny dot 2a dot pl 2010-05-06 17:39 ` [Bug libstdc++/44015] " paolo dot carlini at oracle dot com 2010-05-06 19:44 ` redi at gcc dot gnu dot 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-44015-4-HksHKQEmEY@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).