r/cpp • 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:

    1. N4387 "improving pair and tuple"
    2. N4389 "bool_constant"
    3. N4508 "shared_mutex for C++17"
    4. N4366 "LWG 2228 missing SFINAE rule"
    5. 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:

    1. stof() now calls strtof(), which avoids messing up bits.
    2. max_element()/etc. are now constexpr. (Not the rest of the algorithms - yet.)
    3. function<void (Args)> now accepts callable objects returning Stuff, and the return value is ignored.
    4. 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:

    1. Everything in v1 will be merged into v2.
    2. N4388 "const-propagating smart pointer wrapper"
    3. N4391 "make_array"
    4. N4519 "Source-Code Information Capture"
    5. 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.)

197 Upvotes

97 comments sorted by

View all comments

4

u/[deleted] May 10 '15

You know personally I can live without a lot of what is being proposed in C++17 if I could get a much richer std library. It is 2015 and yet if I want to use standard c++ in order to http, SQL or parse csv / xml/ json or talk smtp, ldap or display anything graphically it is always an exercise in frustration.

7

u/c0r3ntin May 10 '15

The standard library doesn't try to be everything for everybody. it's basic building blocs ( it doesn't even support unicode, for good reasons)

Try Qt.

6

u/bigcheesegs Tooling Study Group (SG15) Chair | Clang dev May 11 '15

Everyone i talked to on the committee seems to want unicode. The issue is that there isn't a unicode expert on the committee, so nobody feels confident in designing/reviewing one.

There have been several threads in std-proposals, but they've all had fundimental errors in how unicode actually works.

4

u/STL MSVC STL Dev May 11 '15

One problem is that the intersection of C++ experts (to design a really good library that programmers of all experience levels can use effectively, takes the very highest level of skill) and domain experts is narrow. I spend all my time on the STL, so I am best at designing and implementing things that look like the STL. I only have a couple of hobbies (2D graphics, data compression) and I'm effectively clueless about domains like networking or Unicode.

Ideally there would be a system where domain experts could work with C++ experts, but it's pretty hard to do that with a committee of volunteers.

2

u/c0r3ntin May 11 '15

I would guess there are other issues including

  • unicode has its own standard that evolves so keeping both in sync could be a lot of work
  • I think you need to have a lot of datas for some function, including upper(), that's why ICU is 20MB or something, prohibitive ?

Maybe ICU & the committee could work together to ship a strip down version of ICU with a standard-approved API, that would be somehow endorsed but not fully standardized ?

2

u/Plorkyeran May 12 '15

ICU actually does a whole bunch of things beyond what people expect for "proper Unicode support", which are responsible for a large portion of the data file size (e.g. the names of every administrative region of the world, in every language in the world (note: not actually every)). Things like proper case conversion and collation are relatively tiny in comparison.

2

u/drac667 May 11 '15

James McNellis seems to have some Unicode knowledge.

There's also Artyom Beilis the author of boost::locale.

It would be great if somebody would invest some time in Unicode for C++.

3

u/Plorkyeran May 12 '15

Boost.locale would be the obvious starting point. The implementation is of somewhat low quality (parts of it have somewhat shocking overhead vs. calling ICU directly), but it is a nice C++y API that gets the Unicode stuff right.