------- 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
