Notice that this is a first Wednesday, but we are meeting in Palo Alto, not San Francisco! Also, this is a different A9 building from the usual discussion-group meetings. It's the same place we were in last August (https://www.meetup.com/ACCU-Bay-Area/events/241820297/), if that helps.
Join Arthur O'Dwyer on a deep dive into Return Value Optimization and related topics. Even C++03 allowed the compiler to "elide" copy construction in certain cases. We'll start with an explanation of the calling convention on a typical machine, showing where the mysterious "return slot" lives, and why it makes sense that C++03 allowed copy elision in certain special cases (but not others). Then we'll show how C++11 (and a subsequent defect report) upped the game by quietly turning the remaining copies into moves, so that the commonly received wisdom these days is that `return std::move(x)` is never necessary and often a pessimization.
...Or is it? We'll show some real-world examples where `return x` quietly copies a large object instead of moving it. We'll explain the little-known notion of a "converting constructor" and the precise way in which C++17 dropped the ball on these examples. Finally, Arthur has implemented a Clang compiler warning (https://reviews.llvm.org/D43322) to detect and suggest fixes for problematic return statements; he'll walk through the relatively painless process of creating that diagnostic, and perhaps inspire you to contribute to Clang yourself!
Arthur O'Dwyer is the author of Mastering the C++17 STL (https://www.packtpub.com/application-development/mastering-c17-stl) and the principal organizer of the ACCU Bay Area meetup. He currently works for Akamai in San Francisco.