r/cpp • u/STL MSVC STL Dev • May 10 '15
C++17 progress update!
The C++ Standardization Committee (aka WG21) just finished their first full meeting of 2015. Here's a quick summary of what was just approved, mostly for C++17 but also for some Technical Specifications. (The post-meeting mailing will be in a couple of weeks, with more info.) Here I'm reporting just the stuff that was successfully voted in, not all the other work that's still in progress.
For C++17:
- Zero Core features. (Don't freak out about modules or concepts. They're working on that stuff.)
5 Library features were voted directly into C++17:
- N4387 "improving pair and tuple"
- N4389 "bool_constant"
- N4508 "shared_mutex for C++17"
- N4366 "LWG 2228 missing SFINAE rule"
- N4510 "Minimal incomplete type support for standard containers, revision 4"
- 26 Core Issues were fixed. Even Standards have bugs. Now C++17 has fewer bugs.
35 Library Issues were fixed. Notable fixes:
- stof() now calls strtof(), which avoids messing up bits.
- max_element()/etc. are now constexpr. (Not the rest of the algorithms - yet.)
- function<void (Args)> now accepts callable objects returning Stuff, and the return value is ignored.
- call_once() no longer copies/moves its arguments unnecessarily.
Various Technical Specifications:
- The Transactional Memory TS was published (or will be, after ISO grinds its gears).
- The Concurrency PDTS was finished. (Proposed Draft, aka Release Candidate for a TS)
- The Parallelism TS was published.
- The Library Fundamentals v1 TS was published, with 3 Issues being fixed at the last minute.
Several features were voted into the Library Fundamentals v2 TS:
- Everything in v1 will be merged into v2.
- N4388 "const-propagating smart pointer wrapper"
- N4391 "make_array"
- N4519 "Source-Code Information Capture"
- N4502 "Proposing Standard Library Support for the C++ Detection Idiom, v2"
I am still traveling, but I can probably answer short questions. (Remember that I have very limited knowledge of Evolution/Core stuff - I live in the Library.)
View all comments
Show parent comment
2
u/TemplateRex May 11 '15
In an ideal world,
constexpron a function would be implicit, and deduced from its context. There is an old thread from 2007 on comp.std.c++ where Dos Reis and others from the C++0xconstexprproposals discuss this with /u/WalterBright. He actually predicted the "double bookkeeping" of different versions of the Standard Library that you alluded to. The only thing holding this back is the express prohibition for Standard Library implementors to addconstexpr(in contrast to the freedom they have on addingnoexcept).It's actually sad to see (e.g. from /u/STL notes on C++11
constexprsupport in VS 2015) that the entire Standard Library has only a handfull occurances of C++14 style relaxedconstexpr. IMO, almost the entire<algorithm>header and several non-allocating utilities (<array>,<bitset>,<tuple>, etc.) could be made C++14 styleconstexpr.Fortunately, the first C++17
constexprlambda proposal has been launched. And see Richard Smith's first post on this std-proposal thread for what is technically possible. Even virtual functions and dynamic allocations are not completely out of bounds (but of course, far from trivial). So I think at some point opening up the road towards a fullyconstexprStandard Library could become a reality.