Effective Modern C++

Table of contents

1. Copyright/Revision History
2. From the Publisher
   1. Using Code Examples
   2. O’Reilly Safari
   3. How to Contact Us
3. Acknowledgments
4. Introduction
   1. Terminology and Conventions
   2. Reporting Bugs and Suggesting Improvements
5. 1. Deducing Types
   1. Item 1: Understand template type deduction.
      1. Case 1: ParamType is a Reference or Pointer, but not a Universal Reference
      2. Case 2: ParamType is a Universal Reference
      3. Case 3: ParamType is Neither a Pointer nor a Reference
      4. Array Arguments
      5. Function Arguments
   2. Item 2: Understand auto type deduction.
   3. Item 3: Understand decltype.
   4. Item 4: Know how to view deduced types.
      1. IDE Editors
      2. Compiler Diagnostics
      3. Runtime Output
6. 2. auto
   1. Item 5: Prefer auto to explicit type declarations.
   2. Item 6: Use the explicitly typed initializer idiom when auto deduces undesired types.
7. 3. Moving to Modern C++
   1. Item 7: Distinguish between () and {} when creating objects.
   2. Item 8: Prefer nullptr to 0 and NULL.
   3. Item 9: Prefer alias declarations to typedefs.
   4. Item 10: Prefer scoped enums to unscoped enums.
   5. Item 11: Prefer deleted functions to private undefined ones.
   6. Item 12: Declare overriding functions override.
   7. Item 13: Prefer const_iterators to iterators.
   8. Item 14: Declare functions noexcept if they won’t emit exceptions.
   9. Item 15: Use constexpr whenever possible.
   10. Item 16: Make const member functions thread safe.
   11. Item 17: Understand special member function generation.
8. 4. Smart Pointers
   1. Item 18: Use std::unique_ptr for exclusive-ownership resource management.
   2. Item 19: Use std::shared_ptr for shared-ownership resource management.
   3. Item 20: Use std::weak_ptr for std::shared_ptr-like pointers that can dangle.
   4. Item 21: Prefer std::make_unique and std::make_shared to direct use of new.
   5. Item 22: When using the Pimpl Idiom, define special member functions in the implementation file.
9. 5. Rvalue References, Move Semantics, and Perfect Forwarding
   1. Item 23: Understand std::move and std::forward.
   2. Item 24: Distinguish universal references from rvalue references.
   3. Item 25: Use std::move on rvalue references, std::forward on universal references.
   4. Item 26: Avoid overloading on universal references.
   5. Item 27: Familiarize yourself with alternatives to overloading on universal references.
      1. Abandon overloading
      2. Pass by const T&
      3. Pass by value
      4. Use Tag dispatch
      5. Constraining templates that take universal references
      6. Trade-offs
   6. Item 28: Understand reference collapsing.
   7. Item 29: Assume that move operations are not present, not cheap, and not used.
   8. Item 30: Familiarize yourself with perfect forwarding failure cases.
      1. Braced initializers
      2. 0 or NULL as null pointers
      3. Declaration-only integral static const and constexpr data members
      4. Overloaded function names and template names
      5. Bitfields
      6. Upshot
10. 6. Lambda Expressions
    1. Item 31: Avoid default capture modes.
    2. Item 32: Use init capture to move objects into closures.
    3. Item 33: Use decltype on auto&& parameters to std::forward them.
    4. Item 34: Prefer lambdas to std::bind.
11. 7. The Concurrency API
    1. Item 35: Prefer task-based programming to thread-based.
    2. Item 36: Specify std::launch::async if asynchronicity is essential.
    3. Item 37: Make std::threads unjoinable on all paths.
    4. Item 38: Be aware of varying thread handle destructor behavior.
    5. Item 39: Consider void futures for one-shot event communication.
    6. Item 40: Use std::atomic for concurrency, volatile for special memory.
12. 8. Tweaks
    1. Item 41: Consider pass by value for copyable parameters that are cheap to move and always copied.
    2. Item 42: Consider emplacement instead of insertion.
13. Index