The specification titles the section "Clock and Time Domains" and
lists both Clock and TimeState in Phase 1 (§104). The
implementation name is TimeState because the
Scheduler owns the writable record and everyone else reads
ReadonlyTimeState. This alias does not wrap, copy, or change
behaviour — Clock and TimeState are the same type (PH-22l).
§9's public name for the time record.
The specification titles the section "Clock and Time Domains" and lists both
ClockandTimeStatein Phase 1 (§104). The implementation name is TimeState because the Scheduler owns the writable record and everyone else reads ReadonlyTimeState. This alias does not wrap, copy, or change behaviour —ClockandTimeStateare the same type (PH-22l).