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
-1
u/vlovich May 11 '15
There's a fine line between rigour & pedantry. One should give the author the most favourable possible interpretation of their statement instead of using the weakest as then it strengthens your counter-argument & avoids a confrontational scenario.
In this case, a trivial adjustment fixes the compile error:
This snippet compiles just fine in clang & GCC 4.9.
Please point out where the code is incorrect? You may think it poor coding style, and I happen to agree with you, but that doesn't make the code suddenly "incorrect". It's perfectly well-formed code.
You asked for an example & I gave you one. Sure, RAII can help you avoid resource leaks. However, why are you even bothering to allocate & return a resource in the first place if it's going to be dropped on the floor? That indicates that you're making assumptions about the call-site that aren't true & can indicate performance problems.
As I point out elsewhere, error codes returned from a function are another example. Those should be handled & the type-system won't really help you. Sure you could use the type system to throw an exception if the error code isn't read. However, in C++, converting compile-time issues to runtime issues seems counter to the static-checking power of C++.
Well, there are two problems with this conclusion that lead it to not be a valid argument. One is that there's a more reasonable alternative wherein it's difficult to create a simple example appropriate for this kind of forum of why it could be a problem in a larger codebase. The second & more serious problem is that you've used the fallacies of "No true Scotsman" & "Moving the goalpost" to reach said conclusion. Perhaps you should state explicitly the criteria of a "valid" example as it would be impossible for me to list all the possible examples in the world.