public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doug dot gregor at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/20599] variadic template support
Date: Tue, 12 Sep 2006 18:27:00 -0000 [thread overview]
Message-ID: <20060912182719.10245.qmail@sourceware.org> (raw)
In-Reply-To: <bug-20599-365@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from doug dot gregor at gmail dot com 2006-09-12 18:27 -------
It's a chicken-and-egg problem. Nobody on the committee wants to standardize
anything that isn't "existing practice," but we only want to accept patches for
features that have been written into the current working draft. How will C++0x
ever move forward?
GCC is uniquely situated to lead the way to C++0x. Our support for C++03 is
excellent, and the code is open and (relatively) accessible to experimenters.
There are patches "out there" for rvalue references, decltype, variadic
templates, and concepts, among other things. If the patch is ready, and we
think the feature is worth pursuing, we should accept the patch. Our acceptance
allows greater experimentation with and understanding of new ideas within the
C++ community and how they interact, and will improve the C++0x language as a
whole. Of course, it also means that GCC will have one of the most mature
implementations of the upcoming C++0x features once C++0x is finally written in
stone.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20599
next prev parent reply other threads:[~2006-09-12 18:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-20599-365@http.gcc.gnu.org/bugzilla/>
2006-09-12 15:36 ` bkoz at gcc dot gnu dot org
2006-09-12 15:51 ` pcarlini at suse dot de
2006-09-12 18:27 ` doug dot gregor at gmail dot com [this message]
2006-09-12 18:29 ` pinskia at gcc dot gnu dot org
2006-09-12 20:30 ` pcarlini at suse dot de
2006-09-13 6:20 ` bkoz at gcc dot gnu dot org
2006-09-15 8:40 ` rguenth at gcc dot gnu dot org
2006-09-25 3:38 ` gdr at integrable-solutions dot net
2006-09-25 3:46 ` fang at csl dot cornell dot edu
2006-09-25 13:00 ` pcarlini at suse dot de
2007-03-10 1:59 ` dgregor at gcc dot gnu dot org
2007-03-10 2:02 ` dgregor at gcc dot gnu dot org
2007-03-12 6:22 ` fang at csl dot cornell dot edu
2007-03-12 9:26 ` pcarlini at suse dot de
2007-03-28 14:30 ` dgregor at gcc dot gnu dot org
2005-03-23 6:01 [Bug c++/20599] New: " bkoz at gcc dot gnu dot org
2005-03-23 15:13 ` [Bug c++/20599] " pinskia 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=20060912182719.10245.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: link
Be 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).