everything and cheap to instantiate CppCon 2023 | Forwarding References Summary 55• Use const MyType& when a read access is only needed – binds to everything and cheap to instantiate • Use both const MyType& Summary 55• Use const MyType& when a read access is only needed – binds to everything and cheap to instantiate • Use both const MyType& and MyType&& for sinks where it is not too expensive – consider MyType Summary 55• Use const MyType& when a read access is only needed – binds to everything and cheap to instantiate • Use both const MyType& and MyType&& for sinks where it is not too expensive – consider MyType

the specialization to create • For class templates, implicit instantiation doesn't necessarily instantiate all the members of the class • The compiler might not generate non-virtual member functions or definition of the corresponding specialization • If you explicitly instantiate a template in one translation unit, you must not explicitly instantiate in another translation unit 62 //- Source file my_foo.cpp

local-recipes-index repositories point to local folders in the filesystem. While users may choose to sync that folder with a git repository or other version control mechanisms, Conan is agnostic to this, conanfile.py 469 Conan Documentation, Release 2.10.1 But the generate() method can explicitly instantiate those generators, use them conditionally (like using one build system in Windows, and another build the package_info() is a CppInfo object, so in most cases it will not be necessary to explicitly instantiate it, and using it as explained in the package_info() section would be enough. This section describes

local-recipes-index repositories point to local folders in the filesystem. While users may choose to sync that folder with a git repository or other version control mechanisms, Conan is agnostic to this, Pkg(ConanFile): generators = "CMakeDeps", "CMakeToolchain" But the generate() method can explicitly instantiate those generators, use them conditionally (like using one build system in Windows, and another build the package_info() is a CppInfo object, so in most cases it will not be necessary to explicitly instantiate it, and using it as explained in the package_info() section would be enough. This section describes

local-recipes-index repositories point to local folders in the filesystem. While users may choose to sync that folder with a git repository or other version control mechanisms, Conan is agnostic to this, Pkg(ConanFile): generators = "CMakeDeps", "CMakeToolchain" But the generate() method can explicitly instantiate those generators, use them conditionally (like using one build system in Windows, and another build the package_info() is a CppInfo object, so in most cases it will not be necessary to explicitly instantiate it, and using it as explained in the package_info() section would be enough. This section describes

local-recipes-index repositories point to local folders in the filesystem. While users may choose to sync that folder with a git repository or other version control mechanisms, Conan is agnostic to this, Pkg(ConanFile): generators = "CMakeDeps", "CMakeToolchain" But the generate() method can explicitly instantiate those generators, use them conditionally (like using one build system in Windows, and another build the package_info() is a CppInfo object, so in most cases it will not be necessary to explicitly instantiate it, and using it as explained in the package_info() section would be enough. This section describes

local-recipes-index repositories point to local folders in the filesystem. While users may choose to sync that folder with a git repository or other version control mechanisms, Conan is agnostic to this, Pkg(ConanFile): generators = "CMakeDeps", "CMakeToolchain" But the generate() method can explicitly instantiate those generators, use them conditionally (like using one build system in Windows, and another build the package_info() is a CppInfo object, so in most cases it will not be necessary to explicitly instantiate it, and using it as explained in the package_info() section would be enough. This section describes

14Copyright © 2020 Bob Steagall K E W B C O M P U T I N G Some Solutions – Per-Container Mutex • Instantiate a per-container mutex and perform updates in a single critical section guarded by the mutex • 16Copyright © 2020 Bob Steagall K E W B C O M P U T I N G Some Solutions – Per-Element Mutex • Instantiate a per-element mutex, acquire the mutexes for all the elements in the update group, then update 17Copyright © 2020 Bob Steagall K E W B C O M P U T I N G Some Solutions – Per-Element Mutex • Instantiate a per-element mutex, acquire the mutexes for all the elements in the update group, then update

syntax of the original manda- tory compiler to instantiate a template at a specific location, allowing us to explicitly tell the compiler when to instantiate the template: 26 2.5 Templates CHAPTER 02: shared variable reading and writing, the introduction of the std::atomic template, so that we instantiate an atomic type, will be an Atomic type read and write operations are minimized from a set of instructions

local-recipes-index repositories point to local folders in the filesystem. While users may choose to sync that folder with a git repository or other version control mechanisms, Conan is agnostic to this, Pkg(ConanFile): generators = "CMakeDeps", "CMakeToolchain" But the generate() method can explicitly instantiate those generators, use them conditionally (like using one build system in Windows, and another build the package_info() is a CppInfo object, so in most cases it will not be necessary to explicitly instantiate it, and using it as explained in the package_info() section would be enough. This section describes