VS 2015 Update 2's STL is C++17-so-far Feature Complete--Stephan T. Lavavej

Good news from the Visual C++ team: in Visual Studio Update 2, they have implemented every C++ Standard Library feature that's been voted into C++11, C++14, and the C++17-so-far Working Paper N4567:

VS 2015 Update 2's STL is C++17-so-far Feature Complete

by Stephan T. Lavavej

From the article:

Update 2's STL fully supports N3462 "SFINAE-Friendly result_of" and LWG 2132 "std::function ambiguity"...

CppCast Episode 42: Intel Tamper Protection with Marc Valle

Episode 42 of CppCast the only podcast for C++ developers by C++ developers. In this episode Rob and Jason are joined by Marc Valle to discuss Intel's Tamper Protection Toolkit which can be used to protect your C++ application from reverse engineering and tampering.

CppCast Episode 42: Intel Tamper Protection with Marc Valle

by Rob Irving and Jason Turner

About the interviewee:

Marc Valle is the technical lead for the Intel (R) Tamper Protection Toolkit. His professional interests include tamper protection, reverse engineering, compilers, security, and privacy. In his free time he can be found staring at the black line at the bottom of the pool preparing for his next competition.

C++ in 2016

A short overview on what is to expect from C++ in 2016:

C++ in 2016

by Jens Weller

From the article:

Like in the previous years, a short outlook into the fresh year regarding C++...

Alex Stepanov

Alex Stepanov retired last week. He’s one of the most prominent members of the C++ community and one of the most innovative contributors to the C++ standard. He was the father of the STL and probably the first promotor of “concepts” as we now know them. Concepts, as specified in the ISO TS, will ship as part of GCC6.0 “any day now.” His work on generic programming goes back in time through Ada (1987), Scheme (1986), and Tecton (1981). See his list of contributions (books, articles, talks, and videos): http://www.stepanovpapers.com/. Without him, we would not have had generic programming as we know it and C++ would have been a very different and poorer language.

For the mathematically oriented among us, I strongly recommend his recent books: Mathematics to Generic Programming with Daniel E. Rose and Elements of Programming with Paul McJones. He got a great sendoff from his most recent employer, A9; they even issued a special stamp in his honor:

 

LLVM/Clang Sprint hosted by Bloomberg

Come and have fun hacking on LLVM, Clang and other projects in the LLVM ecosystem!

Clang/LLVM Sprint Weekend in New York and London

Bloomberg is hosting a sprint weekend on the 6th & 7th of February 2016 in New York and London.

Entrance is free, registration is required! Internet access, food, beverages and mentors will be provided. Bring your own laptop and C++ skills.

"Quick Start" sessions will be provided for those who are new to the project. It's a great opportunity to learn and contribute!

The sessions will run on Saturday from 10:00-22:00 and on Sunday from 10:00-17:00. There will be no access to the facilities between 22:00 on Saturday evening and 10:00 Sunday morning.

New York: https://www.eventbrite.com/e/clangllvm-sprint-hosted-by-bloomberg-registration-20770403837

London: https://www.eventbrite.com/e/clangllvm-sprint-hosted-by-bloomberg-registration-20710913901

A customizable framework -- Andrzej Krzemieński

How to write customizable framework which would work on "practically any type". This article is continuation of author previous post: "Overload resolution".

A customizable framework

by Andrzej Krzemieński

From the article:

We want to provide a function (or a set of overloaded functions) that would ‘do the right job’ for ‘practically any type’, or for ‘as many types as possible’. As an example of such ‘job’ consider std::hash: what we want to avoid is the situation, where you want to use some type X as a key in the standard hash-map, but you are refused because std::hash does not ‘work’ for X. In order to minimize the disappointment, the Standard Library makes sure std::hash works with any reasonable built-in or standard-library type. For all the other types, that the Standard Library cannot know in advance, it offers a way to ‘customize’ std::hash so that they can be made to work with hash-maps.