Crate wake
Expand description
Instance-scoped background wake routing shared by native and headless hosts.
tilo_rt::wake, tilo_host::wake and ui::wake re-export this crate. It
links no async runtime, so a document model can route wakes in a sandboxed
wasm build.
Structs§
- Owed
- A reply owed to a scope’s owner (
WakeHandle::owe). Dropping it says the reply landed: queued for the owner, or the work ended without one. It wakes the owner. - Reply
- The answering end of a request made under a wake scope, such as a system chooser’s. Sending the answer wakes that scope’s event loop, so an answer that arrives while the app is idle is drawn without waiting for input.
- Wake
Event - A weak identity for a queued wake; it never owns an app or its scope.
- Wake
Handle - Captures one scope, or remains detached forever. Unlike a closed scope, detached execution may publish local/headless state without waking a host.
- Wake
Scope - The non-clone owner of one mount incarnation. Drop closes it.
- Wake
Scope Guard - A thread-affine construction/dispatch guard, independent of an App borrow.
- Waking
Sender - The worker’s end of a
waking_channel: every message it sends wakes the scope that opened the channel, so the app drains it on its next sync instead of pumping frames to poll for it.
Enums§
- Wake
Bind Error - Why a platform destination could not be installed.
Functions§
- reply
- A reply channel for a request made now, under the current wake scope.
- waking_
channel - “Wake me when this worker replies”: a channel opened now, under the
current wake scope (the app’s). A worker sends its replies through the
WakingSender; each one wakes the app’s event loop, which drains theReceiverin its next sync. A waiting app paints nothing until a reply lands —needs_animation_frameis for motion, never for polling a worker.