2014:executors_for_c
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
2014:executors_for_c [2013/11/05 18:59] – created jonjagger | 2014:executors_for_c [2016/06/11 14:05] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
Back to [[conference: | Back to [[conference: | ||
\\ | \\ | ||
- | **Title**: | + | **Title**: |
- | **Proposer**: | + | **Proposer**: |
- | **Type**: \\ | + | **Type**: |
- | **Duration**: | + | **Duration**: |
**Description**: | **Description**: | ||
+ | Executors (or schedulers) will be a base building block in C++ | ||
+ | for asynchronous and parallel work. | ||
+ | Executors for asynchronisity are somehow similar to allocators for containers: | ||
+ | They are a very important implementation aspect, but for most people they | ||
+ | are hidden behind the scene.\\ | ||
\\ | \\ | ||
+ | Many programmers don't care more about executors as they care | ||
+ | about allocators: they just take the default implementation and are | ||
+ | generally happy with it.\\ | ||
+ | \\ | ||
+ | Developers concerned with performance however want to have a closer look | ||
+ | to executors, to understand what different design dimensions exist for | ||
+ | executors and what implications they have on performance and programming model.\\ | ||
+ | \\ | ||
+ | This talk will not only present the current proposal for | ||
+ | addition of executors to C++, but also all the background and consequences | ||
+ | of executors for the different (proposed and existing) C++ mechanisms for | ||
+ | concurrency, | ||
+ | \\ | ||
+ | Intended audience:\\ | ||
+ | This talk is for programmers and designers who are interested in some | ||
+ | background for an asynchronous C++ world.\\ | ||
\\ | \\ | ||
\\ | \\ | ||
\\ | \\ | ||
- |
2014/executors_for_c.1383677984.txt.gz · Last modified: 2016/06/11 14:05 (external edit)