The second panel from C++ and Beyond 2012 is now available on Channel 9:
Alexandrescu, Meyers and Sutter – Ask Us Anything
Here is the “Ask Us Anything” panel from C++ and Beyond 2012.
Andrei Alexandrescu, Scott Meyers and Herb Sutter take questions from attendees. As expected, great questions and answers…
Table of contents (click the time codes ([xx:xx]) to hear the answers…):
- message passing primitives in future versions of the standard… [00:00]
- standardized unit testing framework… [02:55]
- std::async… [04:30]
- standard modules proposal… [08:14]
- keyword additions and the standard library… [09:35]
- problems (and solutions) with exceptions… [12:50]
- future of concepts… [22:34]
- std::thread and thread interruption… [23:03]
- when to use the auto keyword (and when not to…)… [25:03]
- more on auto (benefits of reduncancy, type conversion issues with bool to int?)… [29:31]
- const and multithreaded programming, in C++11 const means thread safe, too… [35:00]
- yet more on auto (impact on rampant use and code readability/comprehension)… [42:42]
- compiler type deduction information (compiler switch that prints out auto deduced type information)… [50:18]
- printing out code for review that replaces auto with the actual type… [53:30]
- auto and dynamic memory allocation… [54:59]
- useful, broadly-used concurrency libraries… [57:00]
Maybe not the right place to ask .. but as threads cant be interrupted. How would one go about implementing a program that does two expensive calls, of the same type, and then only waits for the result from the quicker one, not waiting and discarding the slower result. std::async cant be detached..