We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Move, push_back(), and noexcept

Formal Metadata

Title
Move, push_back(), and noexcept
Alternative Title
Move, noexcept, and push_back() and how they relate to each other
Title of Series
Number of Parts
170
Author
License
CC Attribution - NonCommercial - ShareAlike 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
One key feature of C++11 is move semantics with rvalue references. However, combined with other features and guarantees of the standard library the consequences of introducing move semantics turn out to be remarkable. In fact, late in the standardization process this features caused the new concept for exception handling using the new keyword noexcept. The reason was to remain backward compatibility of push_back() for vectors. This talk will jump into the whole mess of this topic of move semantics and exception handling. It give a rough understanding of what move semantics means for class designers and why and how good class design even more becomes an issue with C++11.