pub fn tick_fn_name() -> &'static strExpand description
__lgx_tick(ms) — the page’s clock moves forward by ms, and every timer that time makes due
fires, in due order.
★ ONE IMPLEMENTATION FOR EVERY TIER, WHICH IS THE WHOLE POINT. A browser has real timers and a
test has none, so the obvious build gives the two tiers different code and hopes they agree.
Instead the page keeps its own clock (__LGX_NOW) and every due time in compiled LOGOS, and the
tiers differ only in what calls this: a browser hands it the milliseconds that passed — before
every entry, and when wakeAfter says the earliest timer is due — and Advance time by … calls
it directly. A timer fires at the page time it was armed for, whatever steps the clock took.