Lifetime Safety Profile • Herb plans to revise the Lifetime Safety Profile as part of Cpp2Future of C++?Future of C++? C++ Core Guidelines’ Lifetime Safety ProfileFuture of C++? C++ Core Guidelines’ Simplified borrowing Hylo (formerly Val): Mutable Value SemanticsSwift’s Law of Exclusivity Future of C++? C++ Core Guidelines’ Lifetime Safety Profile Crubit: Adopting Rust’s Type System Simplified borrowing Hylo (formerly Val): Mutable Value SemanticsSwift’s Law of Exclusivity Future of C++? C++ Core Guidelines’ Lifetime Safety Profile Crubit: Adopting Rust’s Type System

FILE I/O: PAST, PRESENT AND FUTURE CPPCON OCTOBER 3RD 2023 GUY DAVIDSON @HATCAT01INTRODUCTIONS • Head of Engineering Practice at Creative Assembly • 1980 – Acorn Atom • ISO/IEC JTC1/SC22/WG21 • BSI buffered file IO? • How do we optimise unbuffered file IO? • How might the standard help us in future?AGENDA • Sub-megabyte days • More RAM, more disk capacity • Moving data into and out of RAM • buffered file IO? • How do we optimise unbuffered file IO? • How might the standard help us in future?SUMMARY • https://wg21.link/p1040 • https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3017.htm

Building a central Go modules repository: GoCenter’s back to the future. @jfrog @ankushchadha111 GopherCon 2019 Lightning Talk Ankush Chadha About me • Dev Manager, Community & Partner Engineering

Rust 是否需要另⼀种“⾊彩”的 Future？ 郭⼦兴，字节跳动服务框架团队研发⼯程师。 作者 Rust 是否需要另⼀种“⾊彩”的 Future？ 标题 Rust 编译器将 async 块翻译成由标准库提供的 Future 类型，⽤户可以⽅便地通过⾃定义 Future 以实现⾮阻塞 的 IO 或并发控制语义。异步执⾏器被允许在任意时刻删除⽣成的 Future 实例以取消正在执⾏的异步操作，但取消 是否需要另⼀种“颜⾊”的 Future 为有副作⽤取消的异步⾏为提供安全保证？ 回顾如何使⽤ Future ⽀持基于 poll 的 IO，以及基于取消 Future 的流程控制 # 基于 Poll 的 Future io-uring 等异步模型让 Future 的取消不 再⽆副作⽤，这可能导致严重的错误 # 不再是⽆副作⽤的取消 # 最终与折中⽅案 引⼊另⼀种“颜⾊”的 Future 以最终解决 Rust 中的异步 Rust 基于 Future trait 实现异步编程 pub trait Future { type Output; fn poll(self: Pin<&mut Self>, cx: &mut Context<'_>) �� Poll; } pub trait Future { type Output;

tornado.autoreload — Automatically detect code changes in development tornado.concurrent — Work with Future objects tornado.log — Logging support tornado.options — Command-line parsing tornado.testing — Unit it is finished, and generally causes some work to happen in the background before triggering some future action in the application (as opposed to normal synchronous functions, which do everything they are returning). There are many styles of asynchronous interfaces: Callback argument Return a placeholder (Future, Promise, Deferred) Deliver to a queue Callback registry (e.g. POSIX signals) Regardless of which

tornado.autoreload — Automatically detect code changes in development tornado.concurrent — Work with Future objects tornado.log — Logging support tornado.options — Command-line parsing tornado.testing — Unit it is finished, and generally causes some work to happen in the background before triggering some future action in the application (as opposed to normal synchronous functions, which do everything they are returning). There are many styles of asynchronous interfaces: Callback argument Return a placeholder (Future, Promise, Deferred) Deliver to a queue Callback registry (e.g. POSIX signals) Regardless of which

it is finished, and generally causes some work to happen in the background before triggering some future action in the application (as opposed to normal synchronous functions, which do every- thing they There are many styles of asynchronous interfaces: • Callback argument • Return a placeholder (Future, Promise, Deferred) • Deliver to a queue • Callback registry (e.g. POSIX signals) Regardless of tornado.concurrent import Future def async_fetch_manual(url): http_client = AsyncHTTPClient() my_future = Future() fetch_future = http_client.fetch(url) def on_fetch(f): my_future.set_result(f.result().body)

it is finished, and generally causes some work to happen in the background before triggering some future action in the application (as opposed to normal synchronous functions, which do every- thing they There are many styles of asynchronous interfaces: • Callback argument • Return a placeholder (Future, Promise, Deferred) • Deliver to a queue • Callback registry (e.g. POSIX signals) Regardless of tornado.concurrent import Future def async_fetch_manual(url): http_client = AsyncHTTPClient() my_future = Future() fetch_future = http_client.fetch(url) def on_fetch(f): my_future.set_result(f.result().body)

thread yfutures/promises: “buffered channel” Promise promise; Future future = promise.Future(); reader.Read(); // Blocks! Channel::Writer writer = channel.Writer(); thread yfutures/promises: “buffered channel” Promise promise; Future future = promise.Future(); reader.Read(); // Blocks! Channel::Writer writer = channel.Writer(); thread yfutures/promises: “buffered channel” Promise promise; Future future = promise.Future(); future.Get(); // Blocks! Channel::Writer writer = channel.Writer();

it is finished, and generally causes some work to happen in the background before triggering some future action in the application (as opposed to normal synchronous functions, which do every- thing they There are many styles of asynchronous interfaces: • Callback argument • Return a placeholder (Future, Promise, Deferred) • Deliver to a queue • Callback registry (e.g. POSIX signals) Regardless of tornado.concurrent import Future def async_fetch_manual(url): http_client = AsyncHTTPClient() my_future = Future() fetch_future = http_client.fetch(url) def on_fetch(f): my_future.set_result(f.result().body)