pub enum TransientBuild {
Ready(TransientSpec),
Future(TransientBuildFuture),
}Expand description
What TransientSourceRegistry::build answers with.
Native builders are pure functions of a TransientContext and
answer Ready — the menu seats in the same frame the
chord was pressed, exactly as before this type existed. A WASM
builder cannot: its build is a guest call on the plugin’s own
actor task, and blocking the editor actor on it would violate
paramount #4. So it answers Future and the host
parks, then seats on the async-landed wake.
Making that difference a value rather than two registries is what
keeps Effect::OpenTransient { source } one code path: the effect
still carries only a name, and neither the chord nor the ex-command
that emits it knows or cares which kind of builder answers.
Variants§
Ready(TransientSpec)
Built synchronously — seat it now.
Future(TransientBuildFuture)
Building off-thread. Err from the future is echoed and the
menu does not open.