Wikipedia has a feature list.
MSVC already supports a good portion of it, as does gcc.
Things I'm excited about:
No modules though, so you still have to write some duplicate code with separate header and implementation files. There are utf-8, utf-16, and utf-32 string literals but still no real unicode support - the standard library still only deals with plain ascii strings. And iostreams is still terrible.
MSVC already supports a good portion of it, as does gcc.
Things I'm excited about:
- Move constructors. If you want to return a vector, you can do so without making a copy of it or relying on the compiler to use the return-value optimization.
- Auto. Like C#'s var. Nice for long, template-y types returned from a function.
- A foreach loop. About time.
- Constructor delegation. No more making an extra function just for shared constructor code.
- Explicitly tell the compiler a function is intended to be an override of a base class virtual function so you don't get screwed by a typo.
- The ">>" in vector<vector<int>> will get parsed correctly instead of forcing you to do the uglier vector<vector<int> >.
- R"Raw\Strings\With\Backslashes\In\Them".
- Smart pointers, hashmaps, threading in the standard library.
- Lambdas and closures.
No modules though, so you still have to write some duplicate code with separate header and implementation files. There are utf-8, utf-16, and utf-32 string literals but still no real unicode support - the standard library still only deals with plain ascii strings. And iostreams is still terrible.