We’re still working on finishing VS 2015 RTM, but we’re definitely done with adding new features, so we can publish final feature tables.  Let’s start with the STL, where we implemented a bunch of stuff after publishing 2015 RC’s features in April.  Whenever I mention C++17 below, I’m referring to the current Working Paper N4527.

    Standard Library     This table of C++14/17 Library features contains new rows for the features that were voted into C++17 in May:    

    “2015 opt-in” means that this is guarded by a macro.  By default, we provide auto_ptr/etc.  If you define _HAS_AUTO_PTR_ETC to 0 project-wide (which you should do via the command line or project file, not via #define), then we won’t provide auto_ptr/etc.  In the next major version, I’m planning to make this opt-out, and in the major version after that, I’m planning to eliminate auto_ptr/etc. entirely.  Now would be a good time to start migrating your code.     “N/A” means that these proposals altered the Standard’s wording, but did not physically affect implementers or users.  I’ve listed them as Not Applicable for the sake of completeness.     Here’s a detailed summary of our status:     Our C99 Standard Library implementation is complete, except for tgmath.h (which is irrelevant in C++) and the CX_LIMITED_RANGE/FP_CONTRACT pragma macros.     On top of that, our C++11 Standard Library implementation is complete.     On top of that, our C++14 Standard Library implementation is complete, except for Expression SFINAE in result_of (N3462) and std::function (LWG 2132), plus 11 more Library Issues.     On top of that, our C++17-so-far Standard Library implementation is complete, except for pair/tuple improvements (N4387) and untimed shared_mutex (N4508), plus 10 Library Issues.     Any remaining exceptions are bugs.  (By the way, we’ve fixed roughly 160 bugs in the STL between 2013 and 2015.  A year ago, I listed the first batch of fixes.  I’ll write about the rest of the fixes soon.)  For example, we’ve implemented every occurrence of constexpr in C++17-so-far’s STL, with a very small number of exceptions, which are tracked by DevDiv#1184873/Connect#1414341 and DevDiv#1188232:    

• (C99) offsetof
• (C++11) numeric_limits<float/double/long double>::quiet_NaN()/signaling_NaN()
• (C++11) mutex’s default constructor
• (C++14) error_category’s default constructor
• (C++14) min()/max()/minmax() for initializer_list
• (C++17) min_element()/max_element()/minmax_element()

    We’ve been focused on achieving Standard conformance, which is higher priority than implementing the various Technical Specifications that are being produced by the Committee.  (We think TSes are important, but the Standard is even more important.)  However, we’ve implemented a couple of TS things: the Filesystem “V3” TS (N4100) and Uniform Container Erasure (N4529 [container.erasure]).     Core Language    

    [RTM] These features were implemented between RC and RTM.     [1] We’re planning to start implementing Expression SFINAE in the compiler immediately after 2015 RTM, and we’re planning to deliver it in an Update to 2015, supported for production use.  (But not necessarily 2015 Update 1.  It might take longer.)     [2] C99 preprocessor support is unchanged.  It’s Partial because while the compiler supports variadic macros, our preprocessor’s behavior doesn’t conform to C99/C++11 in many ways.     [3] “Extended integer types” are listed as Not Applicable because the Standard permits but doesn’t require support for types longer than long long.  We’ve chosen not to support such types, which is conformant behavior.  Neither GCC nor Clang has implemented such types.     [4] “Avoiding/fusing allocations” is listed as Not Applicable because the Standard permits but doesn’t require this optimization.  We’ve chosen not to implement it (at least for now), which is conformant behavior.     A note about C++11 constexpr: this is a large feature with complicated interactions throughout the Core Language, implemented in a compiler codebase undergoing modernization, being shipped for the first time.  It contains bugs/limitations, some of which you might notice, and many of which will be fixed in Updates.  (For example, the compiler is currently unable to emit initializers for non-scalar static constexpr data members, including character arrays.  This scenario has been blocked with a warning-as-error C4579.)  Nevertheless, I’ve chosen to list the compiler’s support for C++11 constexpr as being complete, because the STL is successfully using it, and quite intensively so.  (The STL’s handful of missing constexpr occurrences are due to library-only issues, the absence of magic compiler hooks, and the absence of C++14 extended constexpr loops.)   Finally, we’d like to thank everyone who’s reported bugs during 2015’s development cycle, not just in constexpr but throughout the whole product.  If you encounter any more bugs, please report them via Microsoft Connect or Send A Smile/Frown.   Stephan T. Lavavej Senior Developer – Visual C++ Libraries

stl@microsoft.com