CROSS-PLATFORM PITFALLS AND HOW TO AVOID THEM Erika Sweet (she/her) Microsoft C++ TeamWelcome to CppCon 2020! Visit our table at the Expo Hall https://aka.ms/cppcon/expo • Meet the Microsoft C++ 16th • Dynamic Polymorphism with Metaclasses and Code Injection – Sy Brand • Cross-Platform Pitfalls and How to Avoid Them – Erika Sweet • Effective Remote C++ Development with Codespaces – Nick

Firebird Null Guide NULL behaviour and pitfalls in Firebird SQL Paul Vinkenoog Version 1.2, 30 June 2020 Table of Contents 1. What is NULL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . entire expression NULL. This guide explores the behaviour of NULL in Firebird SQL, points out common pitfalls and shows you how to deal safely with expressions that contain NULL or may resolve to NULL. If NULLs creep into your IF statements.  If you use Firebird 2 or higher, you can avoid all the pitfalls discussed here, simply by using [NOT] DISTINCT instead of the ‘=’ and “<>” operators! • Equals

tests doesn't require re-architecting the inner dependencies 30LESSIONS LEARNED THE POTENTIAL PITFALLS On the journey to making {fmt} a full-fledged named module, I've encountered a couple of stumbling (restricted visibility) This applies to both named modules and header units! 31 . 1THE POTENTIAL PITFALLS Instantiations of templates in user code perform name lookup of dependent entities from outside at module compilation time } 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 31 . 2THE POTENTIAL PITFALLS Two potential solutions: export module M; namespace detail { template void baz(T)

programmers’ toolbox. After learning the foundations, we are then going to discuss some of the pitfalls of pointers (e.g. nullptr’s, double frees, memory leaks). However, with modern C++, we can abstract you don’t have to guess where an asterisk goes) 2.) Show how to use pointers and avoid potential pitfalls a.) Using lots of small examples, ranging from simple to more advanced usages (e.g., function pointers) you don’t have to guess where an asterisk goes) 2.) Show how to use pointers and avoid potential pitfalls a.) Using lots of small examples, ranging from simple to more advanced usages (e.g., function pointers)

com/in/alexdathskovskySIGNED AND UNSIGNED PITFALLS Alex Dathskovsky | alex.dathskovsky@speedata.io | www.linkedin.com/in/alexdathskovskySIGNED AND UNSIGNED PITFALLS: Alex Dathskovsky | alex.dathskovsky@speedata Dathskovsky | alex.dathskovsky@speedata.io | www.linkedin.com/in/alexdathskovsky 256SIGNED AND UNSIGNED PITFALLS: Alex Dathskovsky | alex.dathskovsky@speedata.io | www.linkedin.com/in/alexdathskovsky • what

64.3 Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 65 Pitfalls 358 65.1 Blocking the executor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 including breaks) Segment Duration Async Basics 30 minutes Channels and Control Flow 20 minutes Pitfalls 55 minutes Exercises 1 hour and 10 minutes 16 Format The course is meant to be very interactive minutes. It contains: Segment Duration Async Basics 30 minutes Channels and Control Flow 20 minutes Pitfalls 55 minutes Exercises 1 hour and 10 minutes 350 Chapter 63 Async Basics This segment should take

shells • More accurate IntelliSense in remote scenarios Wed 9/16 12:00 – 13:00 Cross-Platform Pitfalls and How to Avoid Them Erika Sweet – generate_n() venueVisual Studio Agenda 1. Conformance 2. Wednesday 16th • Dynamic Polymorphism with Metaclasses and Code Injection – Sy Brand • Cross-Platform Pitfalls and How to Avoid Them – Erika Sweet • Effective Remote C++ Development with Codespaces – Nick

REQUIRE( list.size() == 1 ); } Multiple asserts Dependency76 Challenges & Pitfalls Testing of The77 Challenges & Pitfalls Testing of The ‣ Flakey tests ‣ Slow tests ‣ Brittle tests ‣ Hard to write78

65.3 Select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 66 Pitfalls 353 66.1 Blocking the executor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 including breaks) Segment Duration Async Basics 30 minutes Channels and Control Flow 20 minutes Pitfalls 55 minutes Exercises 1 hour and 10 minutes 16 Format The course is meant to be very interactive minutes. It contains: Segment Duration Async Basics 30 minutes Channels and Control Flow 20 minutes Pitfalls 55 minutes Exercises 1 hour and 10 minutes 344 Chapter 64 Async Basics This segment should take

Data Structures Live Demonstration References Overview Introduction Persistent Memory Use-Cases Pitfalls Persistent Hash Map Design Goals and Methodology Persistence Performance Results Persistent Transactional 10Introduction Persistent Hash Map Persistent Transactional Data Structures Live Demonstration References Pitfalls of Persistent Memory Architecture Limitations ▶ Caches and registers are expected to remain volatile