c++-tr2

I am having a lot of trouble finding any documentation on the header included with vs2012. I see that it is mentioned here but they don't provide a link on how to use it. What I am really looking for is documentation for how to use it, with the visual studio implementation being preferred. Thanks The <filesystem> header is not part of C++11; it is a proposal for C++ TR2 based on the Boost.Filesystem library. Visual C++ 2012 includes an implementation of the proposed library. See the MSDN documentation for the <filesystem> header and the C++ TR2 proposal on which the implementation is based

I'm reading the documentation of std::experimental::optional and I have a good idea about what it does, but I don't understand when I should use it or how I should use it. The site doesn't contain any examples as of yet which leaves it harder for me to grasp the true concept of this object. When is std::optional a good choice to use, and how does it compensate for what was not found in the previous Standard (C++11). Timothy Shields The simplest example I can think of: std::optional<int> try_parse_int(std::string s) { //try to parse an int from the given string, //and return "nothing" if you

struct T1 {}; struct T2: T1 {}; typedef tr2::direct_bases<T2>::type NEW_TYPE ; should return my something like a touple to bases types. How can I get the nth element of this __reflection_typelist<...>. I search for something like tuple_element for the reflection list. You can use this simple metafunction to turn the typelist into an std::tuple : #include <tr2/type_traits> #include <tuple> template<typename T> struct dbc_as_tuple { }; template<typename... Ts> struct dbc_as_tuple<std::tr2::__reflection_typelist<Ts...>> { typedef std::tuple<Ts...> type; }; At this point, you could work with it as

There is lots of sweet stuff in TR2 . Is that going to be in C++17 ? I understand that TR1 was completed in 2005 and had to wait until C++11 to be standardized. But I also understand that TR2 is already complete? My link to C++17 doesn't mention anything about TR2, but I am hoping... Yakk - Adam Nevraumont Maybe. The point of TR (and now technical specifications) is to allow something to mature independent of the standard iteration process. They can publish a TS, see how it works, see if there are any problems in the implementation and/or use of the feature, and if everything works they can