Skip to main content

Crate day_process

Crate day_process 

Source
Expand description

What a Day process has before, and without, a user interface: its identity and directories, the services that start with it, native notification delivery, and the panic guard every foreign entry point runs through.

Nothing here depends on the widget tree, a toolkit or the reactive runtime, so a background worker, a push handler, an app extension or a command-line tool links this crate alone. day-spec and day-core build on it.

Exactly one copy of this crate may be linked into a process: the registries below are link-time slices, and a second copy would have its own, which the host never runs. The manifest’s links key makes Cargo refuse a dependency graph that resolves two.

Re-exports§

pub use linkme;

Modules§

ffi_guard
Containment for FFI entry points: native callbacks, JNI up-calls, posted-closure trampolines. A Rust panic unwinding out of an extern "C" frame is undefined behavior (an abort), so every backend trampoline runs its body through ffi_guard::contain: a caught panic is reported, the installed recovery hook restores runtime coherence (day-core installs the reactive runtime’s recover_from_panic at boot), and the given default is returned.
routes
A route requested from outside the user interface, at any lifecycle stage, from any thread: the rail a notification tap or a shortcut navigates through (docs/notify.md).
services
Process services that must initialize before a window or reactive tree exists.
storage
Where an app keeps its own files: its data, cache and configuration directories, each a folder named after the app id in the place its platform sets aside for that kind of file (docs/fs.md “Where files live”). Every Day crate that stores files resolves them here, so an app’s database, documents, caches, settings file and remembered window frames sit together and apart from every other app’s.

Enums§

Support
How fully a platform provides something a caller asks about.