public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/22635] OVERLOAD should not be a linked list of trees Date: Sun, 24 Jul 2005 06:28:00 -0000 [thread overview] Message-ID: <20050724045953.16879.qmail@sourceware.org> (raw) In-Reply-To: <20050723202503.22635.pinskia@gcc.gnu.org> ------- Additional Comments From bangerth at dealii dot org 2005-07-24 04:59 ------- I would imagine that in real world, there are either a rather small number of overloads of a name (less than five) or very many (more than 20 or 30). Most code I've seen don't use many overloads (falling into the first class) but there are a few cases in libstdc++, especially in the streams and strings libraries, that use very many overloads. I don't know if knowledge of such overload set size statistics help any in finding an appropriate data structure, though... W. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22635
next prev parent reply other threads:[~2005-07-24 4:59 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-23 20:32 [Bug c++/22635] New: " pinskia at gcc dot gnu dot org 2005-07-23 22:14 ` [Bug c++/22635] " pinskia at gcc dot gnu dot org 2005-07-23 22:33 ` pinskia at gcc dot gnu dot org 2005-07-23 22:42 ` pinskia at gcc dot gnu dot org 2005-07-23 22:45 ` pinskia at gcc dot gnu dot org 2005-07-24 3:36 ` gdr at integrable-solutions dot net 2005-07-24 6:28 ` bangerth at dealii dot org [this message] 2005-07-24 6:50 ` pinskia at gcc dot gnu dot org 2005-07-24 13:16 ` giovannibajo at libero dot it 2005-07-24 13:25 ` pinskia at gcc dot gnu dot org 2005-08-06 6:47 ` pinskia at gcc dot gnu dot org [not found] <bug-22635-6528@http.gcc.gnu.org/bugzilla/> 2009-02-22 14:01 ` steven 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=20050724045953.16879.qmail@sourceware.org \ --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).