Are you wondering why a certain C++ language or library feature works the way it does? how multiple features interact? or whether you've found a bug in the standard?
Here's where you can ask the experts -- including a number of committee members who hang out in this group.
Do you want to propose a new language or library feature and get early feedback on your idea before writing up a detailed proposal?
This is the place to go -- the group for initial discussion of proposed new language and library features that could be considered for future inclusion in ISO C++.
Discussion of a "modules" feature for C++ that packages library interfaces. Modules are intended to improve compilation speed and eliminate problems associated with header-ordering dependencies.
Discussion of networking-related features for C++, including IP addresses, byte ordering, and higher-level constructs.
This is the first of the committee's mailing lists to be made publicly readable. Study Group 5's charter is investigative discussion on what adding transactional memory constructs might look like in C++, and the SG5 group contains useful discussion and pointers to papers, telecons, and other useful information.
Discussion of reflection capabilities for C++, focusing initially on compile-time reflection.
Near-term focus is on the parameter-type-constraints subset of concepts.
Discussion of range-related STL algorithms and other features to replace iterator pairs.
Investigation into whether and how to standardize a way for portable code to check whether a particular C++ product implements a feature yet, as we continue to extend the standard.
Discussion of database-related library interfaces for C++.
Investigation into cataloging and addresses categories of undefined or unspecified behavior.
Investigation into selected low-level graphics/pointing I/O primitives.
Discussion about the C++ FAQ among FAQ editors and anyone else who is interested. For example, when you click on "recommend an improvement" the suggestion email goes here.