📅 2016-Jun-16 ⬩ ✍️ Ashwin Nanjappa ⬩ 🏷️ begin, chrono, cpp, cpp11, decltype, end, error_code, lambda, override, talk, unique_ptr ⬩ 📚 Archive
I recently came across a 2014 talk by Arvid Norberg about the new features in C++11. The video is here and slides are here.
C++ is huge and getting bigger every day. So, I keep discovering interesting new features that I like to note down for use in my own code. Below are my notes from this talk. I do not note aspects that I already know well. This talk has examples that are small but illustrative, so if you hit any of these features, you should see the video to look at the examples.
std::endwork on C arrays too. Note that this is only when the array size is known. So, the array must have been created in the same local scope.
decltypededuces the type of an expression. So its use is in type expressions. For example, as template arguments.
// vector of the return type of function f std::vector<decltype(f())> vals;
autoto deduce type of expression
overrideand it is actually not, compiler will complain.
This smart pointer is not copyable, but movable. It is deleted when pointer goes out of scope.
Many functions create a heap-allocated object and return it. Traditionally, programmers had to worry about the ownership and lifetime of such a returned object. Return it as unique_ptr and forget about these worries.
Also great for storing such heap-allocated objects in containers.
This C++11 feature was something new to me! I did not understand how to apply it either. I might need to study this in future.
error_code represents an error. It has
error_value integral value indicating what is the error. It has
category indicating domain of error value.
category is an abstract base class implementing conversion of
error_value to human readable message.
There are a whole bunch of old C, C++, Unix and POSIX time functions. They are not platform agnostic, have low time resolutions, have no type safety (milliseconds value can be passed to a function that takes in microseconds and so on) and are not monotonic. Monotonic in this context means that if you measure a time before DST is turned on and after it, the latter value should always be larger, though the wall clock may have been turned back by DST.
Chrono introduces a clock with its own epoch (start of life) and its own resolution.
time_point: A point in time relative to epoch. It has its resolution encoded inside it.
time_duration: Difference of two time points. It has its resolution encoded inside it.
Because these types have their resolutions embedded inside, two durations of different resolutions can be added together to produce a duration that has resolution that is highest or higher than both. They can be passed to function that accepts in a different resolution. The template machinery ensures that it all converts correctly.