…_sr_thunk_task<…> …inject_stop_request_thunk<…>(…_sa_task) () at /home/cppcon/c 5 : auto unifex::connect_awaitable(task, receiver auto&) () at /home/cppcon/cppcon24-async 6 : unifex::task a decltype(auto) …_promise::await_transform(…) () at /home/cppcon/cppcon24-async-demo/li 13: auto unifex::connect_awaitable(task, receiver auto&) () at /home/cppcon/cppcon24-async 14: main () at /home/cpp …inject_stop_request_thunk<…>(…_sa_task) () at task.hpp:824 5 : auto unifex::connect_awaitable(task, receiver auto&) () at connect_awaitable.hpp:234 6 : unifex::task async_main<…>(span, auto&

kUIntProp, 4); // ... iZotope Inc.// Button.cpp Button::Button() { GetPropSignal(kText).Connect(this, [] { optional text = GetProperty(kText); assert(text); SetNeedsLayout(); GetPropSignal(kBGColor).Connect(this, update); GetPropSignal(kBorderColor).Connect(this,update); iZotope Inc.// Button.cpp Button::Button() { GetPropSignal(kText).Connect(this, [] { optional GetPropSignal(kBGColor).Connect(this, update); GetPropSignal(kBorderColor).Connect(this,update); iZotope Inc.// Button.cpp Button::Button() { GetPropSignal(kText).Connect(this, [] { optional

BASIC LIFETIME OF AN ASYNC OPERATION SCHEDULER schedule SENDER RECEIVER OPERATION STATE connect start …operation completes… … and notifies receiver … time passes… Implementation details BUILDING BLOCKS OF P2300 concept scheduler: schedule(scheduler) sender; concept sender: connect(sender, receiver) operation_state; concept receiver: set_value(receiver, Values...) void; start(operation_state) void;24 Under the hood of a concurrent operation25 ALL OF THESE SENDERS IMPLEMENT CONNECT ex::sender auto work = ex::when_all( ex::schedule(sched) | ex::then([] { return compute_intensive(0);

Client-side support tornado.websocket.websocket_connect(url: str | HTTPRequest, callback: Callable[[Future[WebSocketClientConnection]], None] | None = None, connect_timeout: float | None = None, on_message_callback: yield websocket_connect(url) while True: msg = yield conn.read_message() if msg is None: break # Do something with msg In the callback style, pass an on_message_callback to websocket_connect. In both styles WebSocket client connection. This class should not be instantiated directly; use the websocket_connect function instead. close(code: int | None = None, reason: str | None = None) → None Closes the websocket

WebSocketHandler.ping() WebSocketHandler.on_pong() WebSocketClosedError Client-side support websocket_connect() WebSocketClientConnection WebSocketClientConnection.close() WebSocketClientConnection.write_message() on a closed connection. Added in version 3.2. Client-side support tornado.websocket.websocket_connect(url: str [https://docs.python.org/3/library/stdtypes.html#str] | HTTPRequest, callback: Callable org/3/library/constants.html#None]] | None [https://docs.python.org/3/library/constants.html#None] = None, connect_timeout: float[https://docs.python.org/3/library/functions.html#float] | None [https://docs.python

your host. – USB device support. VirtualBox implements a virtual USB controller and allows you to connect arbitrary USB devices to your virtual machines without having to install device-specific drivers screens attached to the host system. – Built-in iSCSI support. This unique feature allows you to connect a virtual machine directly to an iSCSI storage server without going through the host system. The 112 for details. – USB over RDP. Via RDP virtual channel support, VirtualBox also allows you to connect arbitrary USB devices locally to a virtual machine which is running remotely on a VirtualBox RDP

your host. – USB device support. VirtualBox implements a virtual USB controller and allows you to connect arbitrary USB devices to your virtual machines without having to install device-specific drivers screens attached to the host system. – Built-in iSCSI support. This unique feature allows you to connect a virtual machine directly to an iSCSI storage server without going through the host system. The 112 for details. – USB over RDP. Via RDP virtual channel support, VirtualBox also allows you to connect arbitrary USB devices locally to a virtual machine which is running remotely on a VirtualBox RDP

Pitfall: Qt4-style Signal/Slot connect() connect( ui->quitButton, SIGNAL(clicked()), this, SLOT(quit())); QObject::connect: No such slot SampleMainWindow::quit() QObject::connect: (sender name: 'quitButton') 'quitButton') QObject::connect: (receiver name: 'SampleMainWindow')54 Safer: Qt5-style Signal/Slot connect() • Use Qt5 pointer-to-member-function connections connect( ui->quitButton, SIGNAL(clicked()) SIGNAL(clicked()), this, SLOT(quit())); // Solution: Qt5-style connections get checked at compile-time: connect( ui->quitButton, &QPushButton::clicked, this, &SampleMainWindow::quit );55 Pitfall: Event processing in

your host. – USB device support. VirtualBox implements a virtual USB controller and allows you to connect arbitrary USB devices to your virtual machines without having to install device-specific drivers screens attached to the host system. – Built-in iSCSI support. This unique feature allows you to connect a virtual machine directly to an iSCSI storage server without going through the host system. The 101 for details. – USB over RDP. Via RDP virtual channel support, VirtualBox also allows you to connect arbitrary USB devices locally to a virtual machine which is running remotely on a VirtualBox RDP

your host. – USB device support. VirtualBox implements a virtual USB controller and allows you to connect arbitrary USB devices to your virtual machines without having to install device-specific drivers screens attached to the host system. – Built-in iSCSI support. This unique feature allows you to connect a virtual machine directly to an iSCSI storage server without going through the host system. The 105 for details. – USB over RDP. Via RDP virtual channel support, VirtualBox also allows you to connect arbitrary USB devices locally to a virtual machine which is running remotely on a VirtualBox RDP