This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of Resolved status.

### 1412. Make monotonic clocks mandatory

Section: 99 [time.clock.monotonic] Status: Resolved Submitter: Switzerland Opened: 2010-08-25 Last modified: 2016-01-28

Priority: Not Prioritized

View all other issues in [time.clock.monotonic].

View all issues with Resolved status.

Discussion:

Addresses CH-21

Monotonic clocks are generally easy to provide on all systems and are implicitely required by some of the library facilities anyway.

[ 2010-11-01 Daniel comments: ]

> Paper n3128 addresses this issue by replacing `monotonic_clock` with `steady_clock`, which is mandatory.

[ 2010-11-13 Batavia meeting: ]

This is resolved by adopting n3191. The original resolution is preserved for reference:

> Make monotonic clocks mandatory.

> Strike 99 [time.clock.monotonic] p.2

> > `2` The class `monotonic_clock` is conditionally supported.

> Change 33.2.4 [thread.req.timing] p.2 accordingly

> > The member functions whose names end in `_for` take an argument that specifies a relative time. Implementations should use a monotonic clock to measure time for these functions. [ Note: Implementations are not required to use a monotonic clock because such a clock may not be available. — end note ]

Proposed resolution:

This is resolved by n3191.