contexts can customize the implementation of standard algorithms for optimal performance. ● Key Features: ● Combining scheduler and policy. ● Minimal, incremental API changes.Combining Scheduler with and 4 are likely to make C++26. 2 and 3 will be beyond C++ 26. These are just some of the likely features that have progressed sufficiently and fit in a talk format, though they still may enter the standard

std::byteswap()  std::to_underlying()  Associative Containers Heterogeneous Erasure  Removed Features  Garbage Collection SupportC++23 Core Language6 Agenda  C++23 Core Language  Explicit Object std::byteswap()  std::to_underlying()  Associative Containers Heterogeneous Erasure  Removed Features  Garbage Collection Support7 Explicit Object Parameters  Instead of implicit this, explicitly std::byteswap()  std::to_underlying()  Associative Containers Heterogeneous Erasure  Removed Features  Garbage Collection Support13 if consteval  Syntax: if consteval { /* A */ } else { /* B */

C++20 STL Features: 1 Year of Development on GitHub Stephan T. Lavavej "Steh-fin Lah-wah-wade" Principal Software Engineer, Visual C++ Libraries stl@microsoft.com @StephanTLavavej 1 Version 1.0 - September down the slide numbers • Part 0: Overview • What's happened in the last year • Part 1: C++20 STL Features • Everything here is Standard, except as noted • Part 2: GitHub Development • For contributors 2019 • github.com/microsoft/STL • Apache License v2.0 with LLVM Exception • Implemented ~50 C++20 features • Majority from our amazing contributors • Extensively reviewed and tested • Released VS 2019

Version 1.0 - September 15, 2020 1 C++20 STL Features: 1 Year of Development on GitHub Stephan T. Lavavej "Steh-fin Lah-wah-wade" Principal Software Engineer, Visual C++ Libraries stl@microsoft.com @StephanTLavavej2 down the slide numbers • Part 0: Overview • What's happened in the last year • Part 1: C++20 STL Features • Everything here is Standard, except as noted • Part 2: GitHub Development • For contributors • github.com/microsoft/STL • Apache License v2.0 with LLVM Exception • Implemented ~50 C++20 features • Majority from our amazing contributors • Extensively reviewed and tested • Released VS 2019

Leveraging C++20/23 Features for Low Level InteractionsOverview In a baremetal environment, we’re going to demonstrate e�ective use of C++ How did we end up with C language HW interactions? What are best e�ectively in line with C++ best practices? �. See also Stroustrup (2023), in referencesKey C++ Safety Features There’s lots, but…. Lifetime Management Smart pointers handle new/delete for you. We’ll mostly

more of your code than your poor overworked development team • Leverage c++’s many compile-time features to build rich, descriptive types • Thank you

__name__ == "__main__": asyncio.run(main()) This example does not use any of Tornado’s asynchronous features; for that see this simple chat room. 5Tornado Documentation, Release 6.5.1 6 Chapter 2. Hello curl_httpclient. Libcurl version 7.22 or higher is required. • pycares is an alternative non-blocking DNS resolver that can be used when threads are not appropriate. Platforms: Tornado is designed for Unix-like although this configuration is not officially supported or recommended for pro- duction use. Some features are missing on Windows (including multi-process mode) and scalability is limited (Even though Tornado

== "__main__": asyncio.run(main()) This example does not use any of Tornado’s asynchronous features; for that see this simple chat room [https://github.com/tornadoweb/tornado/tree/stable/demos/chat] higher is required. pycares [https://pypi.org/project/pycares/] is an alternative non-blocking DNS resolver that can be used when threads are not appropriate. Platforms: Tornado is designed for Unix-like although this configuration is not officially supported or recommended for production use. Some features are missing on Windows (including multi-process mode) and scalability is limited (Even though Tornado

2 Some terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.3 Features overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.4 Supported Enabling DNS proxy in NAT mode . . . . . . . . . . . . . . . . . . . . . 167 9.12.6 Using the host’s resolver as a DNS proxy in NAT mode . . . . . . . . . . 167 9.12.7 Configuring aliasing of the NAT engine Post Installation Configuration . . . . . . . . . . . . . . . . . . . . . . . 216 13.3 Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 13.3.1 The Security Model

2 Some terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 1.3 Features overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.4 Supported Enabling DNS proxy in NAT mode . . . . . . . . . . . . . . . . . . . . . 175 9.11.6 Using the host’s resolver as a DNS proxy in NAT mode . . . . . . . . . . 176 9.11.7 Configuring aliasing of the NAT engine Post Installation Configuration . . . . . . . . . . . . . . . . . . . . . . . 228 13.3 Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 13.3.1 The Security Model