single-threaded server handling multiple clients. • Use the sender/receiver asynchronous framework. • Use a minimalistic sender/receiver networking interface ObjectiveTechAtBloomberg.com © 2024 Bloomberg reserved. • std::execution (sender/receiver): http://wg21.link/p2300 • https://github.com/NVIDIA/stdexec.git • https://github.com/beman-project/execution26 • Sender/receiver networking: http://wg21.link/p2762

resource (aka, scheduler) • A unit of lazy async work (aka, sender) • A completion handler (aka, receiver) • A small, initial set of generic async algorithms: • E.g., then, when_all, sync_wait, let_* nullopt. done_as_error(sender, error) → sender … commutes the done signal into an error.19 SENDER/RECEIVER CONTROL FLOW20 BASIC LIFETIME OF AN ASYNC OPERATION SCHEDULER schedule SENDER Implementation OF AN ASYNC OPERATION SCHEDULER schedule SENDER RECEIVER OPERATION STATE connect start …operation completes… … and notifies receiver … time passes… Implementation details of some algorithm;

ex::_inject::_rcvr_wrapperreceiverreceiver(lldb) co_bt frame #0 : 0x0000555555578278 in unifex::_task::_task<(anonymous k<…>(…_sa_task) () at /home/cppcon/c 5 : auto unifex::connect_awaitable(task, receiver auto&) () at /home/cppcon/cppcon24-async 6 : unifex::task async_main<…>(span, auto& orm(…) () at /home/cppcon/cppcon24-async-demo/li 13: auto unifex::connect_awaitable(task, receiver auto&) () at /home/cppcon/cppcon24-async 14: main () at /home/cppcon/cppcon24-async-demo/src/main

� � � � � � � � � � � : struct Race } name: String , laps: Vecreceiver, a static method fn new(name: &str) -> Self } Self { name: String::from(name), laps: Vec::new � � 59.1 Senders � Receivers � � � � � � � � Rust � � � � � � � � � � � � � � � : SenderReceiverReceiver does not . • send() and recv() return Result. If they return Err, it means the counterpart Sender or Receiver is dropped and the channel is closed . 339

Зав'язані канали 10 хвилин 58.1 Відправники та отримувачі Канали Rust мають дві частини: Sender і Receiver. Дві частини з’єднані через канал, але ви бачите лише кінцеві точки. use std::sync::mpsc; fn можете створити кілька виробників), а Receiver — ні. • send() і recv() повертають Result. Якщо вони повертають Err, це означає, що відповідний Sender або Receiver видалено, а канал закрито. 341 58.2 в інші потоки, але вони не є потокобезпечними. Зазвичай через внутрішню мутабільність: • mpsc::Receiver • Cell • RefCell !Send + Sync До цих типів можна безпечно отримати доступ (через спільні

允许您将函数与新类型相关联。您可以使用“impl”块来执行此操作： struct Race { name: String, laps: Vec, } impl Race { // No receiver, a static method fn new(name: &str) -> Self { Self { name: String::from(name), laps: Vec::new() add_lap(71); race.print_laps(); race.finish(); // race.add_lap(42); } The self arguments specify the ”receiver” - the object the method acts on. There are several common receivers for a method: • “&self”：使 run finish twice. – Beyond variants on self, there are also special wrapper types allowed to be receiver types, such as Box. 13.2 特征（Trait） Rust 让您可以依据特征对类型进行抽象化处理。特征与接口类似： trait Pet { /// Return

do this with an impl block: struct Race { name: String, laps: Vec, } impl Race { // No receiver, a static method fn new(name: &str) -> Self { Self { name: String::from(name), laps: Vec::new() add_lap(71); race.print_laps(); race.finish(); // race.add_lap(42); } The self arguments specify the ”receiver” - the object the method acts on. There are several common receivers for a method: • &self: borrows automatically mean mutability. • mut self: same as above, but the method can mutate the object. • No receiver: this becomes a static method on the struct. Typically used to create con- structors which are called

可讓您將函式與新型別建立關聯。您可以使用 impl 區塊來執行這項操作： struct Race { name: String, laps: Vec, } impl Race { // No receiver, a static method fn new(name: &str) -> Self { Self { name: String::from(name), laps: Vec::new() add_lap(71); race.print_laps(); race.finish(); // race.add_lap(42); } The self arguments specify the ”receiver” - the object the method acts on. There are several common receivers for a method: • &self：使用共 適用 Rust 一般借用規則：可以由一個執行緒以可變方式借用，或者由任意數量的執行緒以不可變 方式借用。 309 第 59 部分 通道 Rust 通道分為兩個部分：Sender 和 Receiver。這兩個部分透過通道相連，但你只能看到端 點。 use std::sync::mpsc; fn main() { let (tx, rx) = mpsc::channel(); tx

add_lap(71); race.print_laps(); race.finish(); // race.add_lap(42); } El argumento self denomina el ”receiver” (receptor) - el objeto sobre cual el método actuará. Hay varios receivers comunes para un método: delimitados 10 minutos 59.1 Transmisores y Receptores Los canales de Rust tienen dos partes: Sender y Receiver. Las dos partes están conectadas a través del canal, pero solo se ven los puntos finales. use decir, puedes crear varios productores), pero Receiver no. • send() y recv() devuelven Result. Si devuelven Err, significa que el homólogo Sender o Receiver se ha eliminado y el canal se ha cerrado. 335

59.1 Transmissores e Receptores Os channels (canais) em Rust têm duas partes: um Sender e um Receiver. As duas partes estão conectadas através do channel, mas você só vê os end-points. use std::sync::mpsc; pode criar vários produtores), mas Receiver (consumidores) não. • send() e recv() retornam Result. Se retornarem Err, significa que a contraparte Sender ou Receiver é descartada e o canal é fechado. threads, mas não são seguros para threads. Normalmente por causa da mutabilidade interior: • mpsc::Receiver • Cell • RefCell !Send + Sync Esses tipos são thread-safe, mas não podem ser movidos