Background • RustBelt Project • Rust Types Overview Rust Semantics • Type System • The own Predict • Exclusive Ownership & Mutable Borrow Examples • Rc Logics • Hoare Logic • Separation Logic Foundations of the Rust Programming Language Coq Proof Assistant: A Formal Proof Management System built on top of built on top of Rust Types Overview Background T &mut T &T mutable borrow {x = 10} {x = 3} x += 1 {x = 4} {True} loop {} {False} Hoare Logic Logics P: x ↦ v Ownership We own “x”, and “x” points to “v”. Disjointness Given “(x ↦ v) ∗ (y ↦ w)”, we know that “x

tested • Released VS 2019 16.5, 16.6, 16.7, 16.8 Preview 3 • GitHub migration ongoing • Build system (native desktop), test suite, issue database • Goal: Complete C++20 in 2020 • No promises, but T* and size_t, but better • spans are implicitly constructible from arrays and vectors • Avoids ownership confusion, accidental pointer arithmetic • span  span; span 🐞 span via GitHub's GraphQL API29 Code: github.com/microsoft/STL • Product: stl/inc, stl/src • Build system: CMake/Ninja • vcpkg submodule acquires Boost.Math for Special Math • tests/std, tests/libcxx,

Hardware-Direct offloading • Can’t carry generic type • Escape safety track Message-Ownership Tracking • Takes message's ownership • Avoid message being dropped. Message-ID Reclaiming • Reclaim Message-ID Senders Receivers Channel Hardware Hardware Producer Consumer Give Ownership Take Ownership Message-ID Reclaiming Message- Ownership Tracking DLB-Assist Channel • Compatible channel interface • Compatible

com/eightfish-org/gutp A Case: GUTP MeBlog is a blog platform for users with the features of open-data and ownership. https://github.com/miketang84/meblog A Case: Meblog Connected to GUTP All Open Data Apps Constitute

Flow-sensitive • Coroutine lifetime checks • Most of CppCoreChecks • Pointer safety analysis • Ownership analysis • Lifetime analysis (preview) • more to come…Looking under the hood • Representing the

Await-Tree 的 应用与真实案例 3 Async Rust 的优势 • 异步编程的共同优势 • async/await 关键字 • 用户态调度 • Async Rust 的独特优势 • Ownership 与 Lifetime • 无栈协程 Async Rust 回顾 Rust 的无栈协程抽象 — Future Async Rust 回顾 • 通过 poll 驱动的状态机 • 组合嵌套为调度单元：

- CallingConv.h • Don’t throw exceptions across the boundary. Explicitly state/document memory ownership rules. • Consider accepting memory alloc/dealloc callbacks – recall previous recommendation. •

）的问题。 解决方案 1 ：获取原始指针（ C * 这种类型的指针） • 解决这个问题需要分两种情况讨论。 • 第一种是，你的 func() 实际上并不需要 “夺走”资源的占有权（ ownership ）。比如 刚才这个例子， func() 只是调用了 p 的 某个成员函数而已，并没有接过掌管对象 生命周期的大权。 解决方案 2 ： unique_ptr 不能拷贝，但可以移动 •

Dates  Time Zones20 Clocks  Several clocks available in :  std::system_clock: wall clock time from system-wide real-time clock  std::steady_clock: guarantees it never goes backwards current time as a time_point. system_clock::time_point tpoint { system_clock::now() }; // Or: auto tpoint { system_clock::now() }; // Convert to a time_t. time_t tt { system_clock::to_time_t(tpoint) }; // aliases: template using sys_time = std::chrono::time_pointsystem_clock, Duration>; // Representation of number of seconds since epoch. using sys_seconds = sys_t

leap_seconds (https://youtu.be/WX3OmVu4lAs) • time_zone and time_zone_link (https://youtu.be/MODhhr7m-5s) • system_clock::now(), file_clock, leap second awareness (https://youtu.be/c7DT28TV0AY)9 Part II: Calendrical requirements.20 C++20’s chrono adds several new clocks ([time.clock]) Existing clocks (pre-C++20) • system_clock • (file_clock) New clocks (in C++20) • utc_clock • tai_clock • gps_clock • (file_clock)21 (file_clock)21 C++20’s chrono adds several new clocks ([time.clock]) Existing clocks (pre-C++20) • system_clock • (file_clock) New clocks (in C++20) • utc_clock • tai_clock • gps_clock • (file_clock)22 Why