From Jason Turner

[time.clock.req]

Diff to HTML by rtfpessoa

Files changed (1) hide show
  1. tmp/tmpzrtimp1e/{from.md → to.md} +15 -12
tmp/tmpzrtimp1e/{from.md → to.md} RENAMED
@@ -6,29 +6,32 @@ clock’s `time_point` is referred to as the clock’s *epoch*. A clock
6
  shall meet the requirements in Table  [[tab:time.clock]].
7
 
8
  In Table  [[tab:time.clock]] `C1` and `C2` denote clock types. `t1` and
9
  `t2` are values returned by `C1::now()` where the call returning `t1`
10
  happens before ([[intro.multithread]]) the call returning `t2` and both
11
- of these calls occur before `C1::time_point::max()`. this means `C1` did
12
- not wrap around between `t1` and `t2`.
13
 
14
- The relative difference in durations between those reported by a given
15
- clock and the SI definition is a measure of the quality of
16
- implementation.
 
 
 
17
 
18
  A type `TC` meets the `TrivialClock` requirements if:
19
 
20
  - `TC` satisfies the `Clock` requirements ([[time.clock.req]]),
21
  - the types `TC::rep`, `TC::duration`, and `TC::time_point` satisfy the
22
- requirements of `EqualityComparable` (Table [[equalitycomparable]]),
23
- `LessThanComparable` (Table [[lessthancomparable]]),
24
- `DefaultConstructible` (Table [[defaultconstructible]]),
25
- `CopyConstructible` (Table [[copyconstructible]]), `CopyAssignable`
26
- (Table [[copyassignable]]), `Destructible` (Table [[destructible]]),
 
27
  and the requirements of numeric types ([[numeric.requirements]]).
28
- this means, in particular, that operations on these types will not
29
- throw exceptions.
30
  - lvalues of the types `TC::rep`, `TC::duration`, and `TC::time_point`
31
  are swappable ([[swappable.requirements]]),
32
  - the function `TC::now()` does not throw exceptions, and
33
  - the type `TC::time_point::clock` meets the `TrivialClock`
34
  requirements, recursively.
 
6
  shall meet the requirements in Table  [[tab:time.clock]].
7
 
8
  In Table  [[tab:time.clock]] `C1` and `C2` denote clock types. `t1` and
9
  `t2` are values returned by `C1::now()` where the call returning `t1`
10
  happens before ([[intro.multithread]]) the call returning `t2` and both
11
+ of these calls occur before `C1::time_point::max()`.
 
12
 
13
+ [*Note 1*: This means `C1` did not wrap around between `t1` and
14
+ `t2`. *end note*]
15
+
16
+ [*Note 2*: The relative difference in durations between those reported
17
+ by a given clock and the SI definition is a measure of the quality of
18
+ implementation. — *end note*]
19
 
20
  A type `TC` meets the `TrivialClock` requirements if:
21
 
22
  - `TC` satisfies the `Clock` requirements ([[time.clock.req]]),
23
  - the types `TC::rep`, `TC::duration`, and `TC::time_point` satisfy the
24
+ requirements of `EqualityComparable` (Table 
25
+ [[tab:equalitycomparable]]), `LessThanComparable` (Table 
26
+ [[tab:lessthancomparable]]), `DefaultConstructible` (Table 
27
+ [[tab:defaultconstructible]]), `CopyConstructible` (Table 
28
+ [[tab:copyconstructible]]), `CopyAssignable` (Table 
29
+ [[tab:copyassignable]]), `Destructible` (Table  [[tab:destructible]]),
30
  and the requirements of numeric types ([[numeric.requirements]]).
31
+ \[*Note 3*: This means, in particular, that operations on these types
32
+ will not throw exceptions. — *end note*]
33
  - lvalues of the types `TC::rep`, `TC::duration`, and `TC::time_point`
34
  are swappable ([[swappable.requirements]]),
35
  - the function `TC::now()` does not throw exceptions, and
36
  - the type `TC::time_point::clock` meets the `TrivialClock`
37
  requirements, recursively.