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

talk results in the improvement of Rust for everyone! Introduction Language Library Tooling Nightly features A general priority is to stabilize them (or to find alternatives): https://github.com/Rus RUSTC_BOOTSTRAP. The rest of this talk focuses on things that are not in nightly. Language Library Tooling Nightly features cfg(no_fp_fmt_parse) cfg(no_global_oom_handling) cfg(no_rc) cfg(no_sync) Language Library Modularization of core and alloc The kernel does not need a range of core/alloc features. Configuring them off is important for correctness, code size… Likely useful for other domains

� � � � � � � � � � � � � � � � � � � : cargo init concurrency cd concurrency cargo add tokio --features full cargo run � � � � � � � � � : • � � � ) � � � � � � �� � � � � � � � � � � � � � � � � � . • � � � � � � � � � � � � � � � � � � � � � : ” stable”� ”beta ” � � ” nightly ”. • � � � � � � � � � � � � � � ” nightly ” � � � � � � � � � � � � � ” beta ” � � � � � � � � � � � � � � � � � ” stable � � � � � � � � � � � � � � � � � � � � � � � std::error::Error � � � � � � � � � � � no_std � � nightly � � � � � � � � � . 29.6 thiserror � anyhow � � � thiserror � anyhow crate � � � � � � � � � �

src/main.rs para experimentar con ellos: cargo init concurrency cd concurrency cargo add tokio --features full cargo run Horario del curso: • Mañana (3 horas y205 minutos, incluidos los descansos) Sección nuevas funciones. • Hay tres canales de lanzamiento: ”stable”, ”beta” y ”nightly”. • Las funciones nuevas se prueban en ”nightly”, y ”beta” es lo que se convierte en ”estable” cada seis semanas. • Las no_std, ten en cuenta que el trait std::error::Error de momento solo es compatible con no_std en nightly. 29.6 thiserror y anyhow The thiserror and anyhow crates are widely used to simplify error handling

para src/main.rs para experimentá-los: cargo init concurrency cd concurrency cargo add tokio --features full cargo run Agenda do curso: • Morning (3 hours and 20 minutes, including breaks) Segment funcionalidades. • Existem três canais de lançamento: ”stable”, ”beta” e ”nightly”. • Novos recursos estão sendo testados em ”nightly”, ”beta” é o que se torna ”stable” a cada seis semanas. • Dependências no_std, tenha em mente que o trait std.error::Error é atualmente compatível com no_std apenas em nightly. 29.6 thiserror e anyhow Os crates thiserror e anyhow são amplamente utilizados para simplificar