You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b14a2ba
Browse filesBrowse the repository at this point in the historyBrowse files
✨ Run spawned document work concurrently with <All>
`<All>` runs its direct `<Spawn>` children at the same time and waits for
all of them. Both names are engine structural syntax, so no repository
file, registration, bundle or Plugin can supply either, and they work in
ordinary and admitted generated XMD alike.
One shared pure rule decides the whole structure from source — paired
forms, no props, at least two spawns, blank text only between them, no
`<Spawn>` outside its `<All>`, and no `<Return>` or `<Break>` reaching
past a spawn — and expansion, non-executing validation and the
whole-fragment preflight read the same result, so a malformed construct
starts no child anywhere.
Each child is a durable coroutine of the one that reached the `<All>`,
allocated in source order by the existing `durableAll()` join, with its
own binding environment, live overlay, eval scope, block counter, output
buffer, failure ledger, hide set and expansion path. Nothing merges back.
`<All>` appends the renderings in authored order only after every child
succeeds, so completion order may decide when records append and never
what the document renders. The first failure cancels and joins the rest,
publishes nothing, and fabricates no completion.
Capability-backed identity becomes branch-local, which is what the
Story's own `<All><Spawn><Session>` example needs. Canonical import
frames and provider answer windows were kept as one execution-wide
last-open stack, so two children resolving at once could have one child's
selection land in the other's frame — an ordinary `<Session>` in each
branch then named no durable identity at all. Both stacks are now owned
per Effection scope: nesting inside one scope still hides its parent
until it closes, sibling branches have independent tops, closing or
cancelling one neither clears nor authorizes the other, and a provider
installation may answer in two open windows while a second, different
answer in either still refuses. The scope is a private key and reaches no
document, component or provider.
`All` and `Spawn` join the two frozen complete structural-vocabulary
expectations, which is what failed the earlier weights run.
0 commit comments