"Emotional Code" https://youtu.be/uloVXmSHiSo Checking what doesn't need to be checked if (pPolicy){ delete pPolicy; } auto int_vals = std::vector(); assert (int_vals.empty()); 1 2 3 4 "I can't be Tests" https://youtu.be/FjwayiHNI1w 2021: Me, "The Unit Tests Strike Back" https://youtu.be/N2YJ4D7O7Oc 2022: Me, "It's a Bug Hunt" https://youtu.be/P8qYIerTYA0 2015: Titus Winters & Hyrum Wright, "All

compiler.runtime field will change based on the build_type value so in that case you will also want to delete the compiler runtime field like so: def package_id(self): if self.settings.os in ["Windows","WindowsStore"] _check_conan check_write_conan = _check_conan check_delete_conan = _check_conan check_read_package = _check_package check_write_package = _check_package check_delete_package = _check_package The module has to recipe. – check_write_conan() is used to decide whether to allow write access to a recipe. – check_delete_conan() is used to decide whether to allow a recipe’s deletion. – check_read_package() is used to

compiler.runtime field will change based on the build_type value so in that case you will also want to delete the compiler runtime field like so: def package_id(self): if self.settings.os in ["Windows","WindowsStore"] _check_conan check_write_conan = _check_conan check_delete_conan = _check_conan check_read_package = _check_package check_write_package = _check_package check_delete_package = _check_package The module has to recipe. – check_write_conan() is used to decide whether to allow write access to a recipe. – check_delete_conan() is used to decide whether to allow a recipe’s deletion. – check_read_package() is used to

compiler.runtime field will change based on the build_type value so in that case you will also want to delete the compiler runtime field like so: def package_id(self): if self.settings.os in ["Windows","WindowsStore"] the generated Conan traces file and a parameter --output to indicate the output file. You can also, delete the traces.log` file` otherwise while the CO- NAN_TRACE_FILE is present, any Conan command will keep config home $> /home/user/.conan • Create all missing configuration files: $ conan config init • Delete the existing configuration files and create all configuration files: $ conan config init --force

compiler.runtime field will change based on the build_type value so in that case you will also want to delete the compiler runtime field like so: def package_id(self): if self.settings.os in ["Windows","WindowsStore"] the generated Conan traces file and a parameter --output to indicate the output file. You can also, delete the traces.log` file` otherwise while the CO- NAN_TRACE_FILE is present, any Conan command will keep config home $> /home/user/.conan • Create all missing configuration files: $ conan config init • Delete the existing configuration files and create all configuration files: $ conan config init --force

compiler.runtime field will change based on the build_type value so in that case you will also want to delete the compiler runtime field like so: def package_id(self): if self.settings.os in ["Windows","WindowsStore"] the generated Conan traces file and a parameter --output to indicate the output file. You can also, delete the traces.log` file` otherwise while the CO- NAN_TRACE_FILE is present, any Conan command will keep config home $> /home/user/.conan • Create all missing configuration files: $ conan config init • Delete the existing configuration files and create all configuration files: $ conan config init --force

compiler.runtime field will change based on the build_type value so in that case you will also want to delete the compiler runtime field like so: def package_id(self): if self.settings.os in ["Windows","WindowsStore"] the generated Conan traces file and a parameter --output to indicate the output file. You can also, delete the traces.log` file` otherwise while the CO- NAN_TRACE_FILE is present, any Conan command will keep config home $> /home/user/.conan • Create all missing configuration files: $ conan config init • Delete the existing configuration files and create all configuration files: $ conan config init --force

compiler.runtime field will change based on the build_type value so in that case you will also want to delete the compiler runtime field like so: def package_id(self): if self.settings.os in ["Windows","WindowsStore"] the generated Conan traces file and a parameter --output to indicate the output file. You can also, delete the traces.log` file` otherwise while the CO- NAN_TRACE_FILE is present, any Conan command will keep config home $> /home/user/.conan • Create all missing configuration files: $ conan config init • Delete the existing configuration files and create all configuration files: $ conan config init --force

compiler.runtime field will change based on the build_type value so in that case you will also want to delete the compiler runtime field like so: def package_id(self): if self.settings.os in ["Windows","WindowsStore"] the generated Conan traces file and a parameter --output to indicate the output file. You can also, delete the traces.log` file` otherwise while the CO- NAN_TRACE_FILE is present, any Conan command will keep config home $> /home/user/.conan • Create all missing configuration files: $ conan config init • Delete the existing configuration files and create all configuration files: $ conan config init --force

^~~~~~The compiler will generate Special Member Functions (SMFs) for you 1. Defining some SMFs may delete or disable some others 2. Special Member Functions T(T const&) T() T(T&&) operator=(T const&) Gadget* gadget; Widget() : age(42), gadget(new Gadget()) {} ~Widget() { delete gadget; } }; std::cout << widget.name << "\n"; std::cout << widget.age << "\n"; std::cout << Gadget* gadget; Widget() : age(42), gadget(new Gadget()) {} ~Widget() { delete gadget; } }; std::cout << widget.name << "\n"; std::cout << widget.age << "\n"; std::cout <<