What will C++17 be?
docs.google.com
What will C++17 be?
1–10 of 86 posts
Re: What will C++17 be?
#2and when would c++ 17 come?
Re: What will C++17 be?
#3How about making the language more accessible to newcomers by providing a sane default way of doing package management and builds. Go is a great example of both things done reasonably well out of the box.
Re: What will C++17 be?
#4and when would c++ 17 come?
c++11 came in 2011. c++14 came in 2014. Seeing a pattern yet?
Re: What will C++17 be?
#5and when would c++ 17 come?
Somewhere in 2017.
Re: What will C++17 be?
#6Re: What will C++17 be?
#7The last slide is worth reading (and avoid doing) and most of it applies to much more than committees for programming languages.
Re: What will C++17 be?
#8Earlier quoted context omitted.
c++11 came in 2011. c++14 came in 2014. Seeing a pattern yet?
When we'll have a compiler support - this is what really matters, especially for those who use MSVC... It is 2015 and we still don't have a full C++11 support.
FWIW, Clang and GCC support all C++11 features.
Re: What will C++17 be?
#9How about making the language more accessible to newcomers by providing a sane default way of doing package management and builds. Go is a great example of both things done reasonably well out of the box.
From where I'm standing, C++ package management is already quite nicely solved by what we call package managers in the linux world. You know, portage, aptitude, etc.