An implicit time model is the execution behavior a language or runtime provides by default. It describes ordering and repetition: sequential statements run in sequence, asynchronous events start new timelines, and actions run as often as called. section 17.16
The default model is useful but may not match a problem. Programs can create a better-fitting model by coordinating shared resources and manipulating ordering or repetition as first-class concerns. section 17.1 section 17.16
Common explicit time controls include:
- Queue callbacks without creating new timelines for asynchronous work. section 17.16
- Use JustOnce() to ensure an action runs only once, even when called repeatedly. section 17.16
- Use Cut() or DroppingQueue() to constrain how repeated calls are handled. section 17.16
Changing repetition behavior
Calling JustOnce(a) three times invokes the resulting action only once; a regular action would execute each time it is called.
