them in our projects?The include directive ● Include directive: “Tells the preprocessor to include the contents of a specified file at the point where the directive appears.” #include error generated. Around ~350k lines after the include is replaced by the contentsThe include directive - cont’d When invoking the compiler, it needs to be able to resolve the location of #included ○ Typically handled by build system / package manager hello_world.cpp hello_world.oThe include directive - cont’d clang++ -std=c++20 -o hello_world.cpp.o -c hello_world.cpp hello_world.cpp:1:10: fatal

assertion in a program should not alter the correctness of that program The Contracts Prime Directive130 Copyright (c) Timur Doumler | @timur_audio | https://timur.audio • The presence Adding a contract assertion that is not checked can't cause runtime overhead The Contracts Prime Directive131 Copyright (c) Timur Doumler | @timur_audio | https://timur.audio • The presence contract assertion, or a subsequent check of the same contract assertion The Contracts Prime Directive132 Copyright (c) Timur Doumler | @timur_audio | https://timur.audio • The presence

Application or tornado.template.Loader constructors, for a template file with the {% autoescape None %} directive, or for a single expression by replacing {{ ... }} with {% raw ...%}. Additionally, in each of these only available in templates invoked via {% module Template(...) %}. Unlike the {% include ... %} directive, template modules have a distinct namespace from their containing template - they can only see the through. Defaults to "xhtml_escape". Can be changed on a per-template basis with the {% autoescape %} directive. • compiled_template_cache: Default is True; if False templates will be recompiled on every re-

false positive May be bad rule for tools Hard Easy MISRA tools, CG Meta Hard Hard Neither, META directive; Code guidelines Obvious rules, but hard to verify Might not be a good rule anyway Need a new [[intention::] [[intention::] attribute Stage 2: collate • Category • Mandatory: 8 • Required: 12 • Advisory: 12 • Directive: 5 • Decidable by humans • Easy: 27 • Medium: 1 • Complex: 20 • Unknown yet: 9 • Decidable via automated It is not visible in code and is not visible for code analysis tools Too high level for C++CG? Directive for tools/MISRA Agenda 1. Current status of C++ safety: MISRA and C++ CG 2. Parallel Safety rules

Test Macros   Immediate Functions – consteval  constinit  Class Enums and using Directive  Text Formatting  Math Constants  std::source_location  [[nodiscard(reason)]]  Bit Operations Forces constant initialization  ✔ E.g.: constinit const char* a { ... };74 Class Enums and using Directive  Example: enum class CardTypeSuit { Clubs, Diamonds, Hearts, Spades }; std::string_view GetString(const  Feature Test Macros  Immediate Functions – consteval  constinit  Class Enums and using Directive  Text Formatting  Math Constants  std::source_location  [[nodiscard(reason)]]  Bit Operations

Application or tornado.template.Loader constructors, for a template file with the {% autoescape None %} directive, or for a single expression by replacing {{ ... }} with {% raw ...%}. Additionally, in each of these only available in templates invoked via {% module Template(...) %}. Unlike the {% include ... %} directive, template modules have a distinct namespace from their containing template - they can only see the through. Defaults to "xhtml_escape". Can be changed on a per-template basis with the {% autoescape %} directive. compiled_template_cache: Default is True; if False templates will be recompiled on every request

uint32_t value = 0; value |= 0x1; value &= ~(0x1);Break from your #defined habits Preprocessor directive #de�ne is incredibly dangerous …But it’s also not unusual to come across macros and constants via REPLACE_BITS(x, mask, bits) ((x & (~(mask))) | (bits &Break from your #defined habits Preprocessor directive #de�ne is incredibly dangerous …But it’s also not unusual to come across macros and constants via

(roughly) as • A source file, • Plus with all the headers and source files included via the #include directive, • Minus any source lines skipped by conditional inclusion preprocessing directives (#ifdef), directives are executed, and macro invocations are expanded • each file included by an #include directive is processed by Phases 1 through 4, recursively • all preprocessing directives are removedCopyright

etc. In case you don’t know…8 CppCon 2021 | • Apache httpd modules (DSO modules) – LoadModule directive • C extension for CPython (.pyd on Windows) – import module_name • Java Native Interface (JNI)

inline namespace, std::literals; they must be imported into the current scope by means of a using directive: – using namespace std; imports everything in the standard library, including all the literals