Studio Agenda 1. Conformance 2. Code Safety 3. Cross-platform development 4. Developer and Team Productivity Visual Studio Agenda 1. Conformance 2. Code Safety 3. Cross-platform development 4. Developer 3:15pm Why does std::format do that? Charlie – _1 Tue, Oct 26 – 4:45pm / Wed, Oct 27 – 12:30pm In-memory and Persistent Representations of C++ Gabriel Dos Reis – `Online _2 💡 Feature complete • C++23 🐱‍🏍�C++23 with /std:c++latest Visual Studio Visual Studio Agenda 1. Conformance 2. Code Safety 3. Cross-platform development 4. Developer and Team Productivity Static Analysis ✴ New and improved

Fly.io, and Embark), even it has paid contributors! Tokio is good enough Tokio Tokio's APIs are memory-safe, thread-safe, and misuse-resistant. This helps prevent common bugs, such as unbounded queues Software Enqueue Software Producer Consumer Consumer Consumer • Synchronization latency • Memory/Cache latency • CPU cycles latency DLB ： Dynamic Load Balance DLB Enqueue Logic Head and Tail Load Balancer Producer Producer Consumer Consumer Consumer • No Synchronization latency • No memory/cache latency • No CPU cycles DLB-Assist Channel Intro Hardware Senders Receive Senders Senders

13 May 11 Jun 08 Jul 13 Aug 10 Sep 14 Oct 12 Nov 09 Dec 1416 Why calendrical types? Type Safety The “simple” calendrical types (e.g., day, month, year) are very straightforward – what’s the as the day and 28 as the year in the implementation! Have these “simple” types improves type safety as we can make sure we are interpreting these values as the appropriate type.17 Why calendrical Brand & Christopher Di Bella (Google) • Static Analysis and Program Safety in C+ +: Making it Real – Sunny Chatterjee • In-memory and Persistent Representations of C++ – Gabriel Dos Reis (online 27th)

safe language But, like C/C++, Rust is also an unsafe language There are guaranteed memory safety, thread safety, ... There are plenty of unsafe codes in Rust’s standard library. use after free data

dereference • more to come.. Flow-sensitive • Coroutine lifetime checks • Most of CppCoreChecks • Pointer safety analysis • Ownership analysis • Lifetime analysis (preview) • more to come…Looking under the hood Brand & Christopher Di Bella (Google) • Static Analysis and Program Safety in C+ +: Making it Real – Sunny Chatterjee • In-memory and Persistent Representations of C++ – Gabriel Dos Reis (online 27th)

Docker CP vulnerability Pod Isolation Challenges • Noisy neighbor −Impact performance on CPU, Memory, Bandwidth, Buffer IO, PIDs, File descriptors # kubectl run --rm -it bb --image=busybox sh / # abstracts the common virtualization components which implements a Rust-based VMM. • Written in Rust: Memory-safe language • Secure: Minimal hardware emulation • Flexible: Easy to customize to fit various network performance similar to C • Memory management without garbage collection • Designed for systems programming Rust is a multi-paradigm programming language focused on performance and safety, especially safe concurrency

mdspan (= slice) std::mdspan49  Example: int* data { /* ... */ }; // View data as contiguous memory representing 2 rows of 2 ints each auto mySpan { std::mdspan(data, 2, 2) }; // Access data from undeclare_reachable()  declare_no_pointers()  undeclare_no_pointers()  get_pointer_safety()  enum pointer_safety  Available since C++11  Not aware of any use of this API  Removed from C++23105

Cross platform - Performance - Thread Safe - Memory Safe - Love 利用 Rust 重塑移动应用开发 Rust 在移动应用 开发中的应用 Why Rust? - Cross platform - Performance - Memory Safe - Love 利用 Rust 重塑移动应用开发 PhoTto / image platforms is increasingly gaining attention from developers. With its impressive performance, memory safety, and concurrency features, Rust has become an ideal choice for building high-performance mobile

易用 可靠 Why Rust ？ Performance • Blazingly fast and memory-efficient • No runtime or garbage collector Reliability • Guaranteed memory safety • “Fearless Concurrency” Productivity • Modern development