paletatiptip

http://CppCon.org
—
Presentation Slides, PDFs, Source Code and other presenter materials are available at: https://github.com/cppcon/cppcon2016
—
There has always been great interest in imperative compile-time control flow: as an example, consider all the existing `static_if` proposals and the recently accepted `constexpr_if` construct for C++17.

What if you were told that it is actually possible to implement imperative control flow in C++14?

In this tutorial, the implementation and design of a compile-time `static_if` branching construct and of a compile-time `static_for` iteration construct will be shown and analyzed. These constructs will then be compared to traditional solutions and upcoming C++17 features, examining advantages and drawbacks.
—
Vittorio Romeo
Bloomberg LP
Software Engineer
London, UK
Vittorio Romeo is an Italian 21 year old Computer Science student at "Università degli Studi di Messina". He began programming at a very young age and is now a C++ enthusiast. While following the evolution of the C++ standard and embracing the newest features, he worked on several open-source projects, including modern general-purpose libraries and free cross-platform indie games. Vittorio is an active member of the C++ community: he participated as a speaker at CppCon 2014/2015, ++it Florence 2015 and at his local Linux Day 2013/2014 events, as a Student/Volunteer at C++Now 2015, and as part of Meeting C++ 2015's student program. He currently maintains a YouTube channel featuring well-received modern C++11 and C++14 tutorials. When he's not writing code, Vittorio enjoys weightlifting and fitness-related activities, competitive/challenging computer gaming and good scifi movies/TV-series.
—
Videos Filmed & Edited by Bash Films: http://www.BashFilms.com

http://www.Cppcon.org
—
Presentation Slides, PDFs, Source Code and other presenter materials are available at: https://github.com/cppcon/cppcon2015
—
During January 2015, Sean Parent posted a very interesting short piece of code on Twitter. The code iteratively iterates at compile-time over any number of function arguments, forwarding them one by one to a callable object.

How does this code work? What are the possible use cases? Can we make it even more generic and useful?

My talk answers all of the questions above, using independently compiled chronologically sequential code segments that show the audience the analysis and improvement process of `for_each_argument`.
—
Vittorio Romeo is an Italian 20 year old Computer Science student at "Università degli Studi di Messina".

He began programming at a very young age and soon became a C++ enthusiast. While following the evolution of the C++ standard and embracing the newest features, he worked on several open-source projects, including modern general-purpose libraries and free cross-platform indie games.

Vittorio is an active member of the C++ community: he participated as a speaker at CppCon 2014, as a Student/Volunteer at C++Now 2015, as a speaker at Italian C++ Meeting 2015 and as a speaker at his local city's Linux Day 2013 and 2014 events.

He currently maintains a YouTube channel featuring well-received modern C++11 and C++14 tutorials.

When he's not programming, Vittorio enjoys weightlifting and fitness-related activities, competitive/challenging computer gaming (CS:GO, Quake, LoL, Touhou, ...), and good sci-fi movies/tv-series (Firefly, Fringe, Futurama, ...).
—
Videos Filmed & Edited by Bash Films: http://www.BashFilms.com