tmp/tmpo5i1n509/{from.md → to.md}
RENAMED
|
@@ -1,18 +1,18 @@
|
|
| 1 |
-
###
|
| 2 |
|
| 3 |
-
This
|
| 4 |
literals. The suffixes `h`, `min`, `s`, `ms`, `us`, `ns` denote duration
|
| 5 |
values of the corresponding types `hours`, `minutes`, `seconds`,
|
| 6 |
`milliseconds`, `microseconds`, and `nanoseconds` respectively if they
|
| 7 |
-
are applied to
|
| 8 |
|
| 9 |
-
If any of these suffixes are applied to a floating-point
|
| 10 |
result is a `chrono::duration` literal with an unspecified
|
| 11 |
floating-point representation.
|
| 12 |
|
| 13 |
-
If any of these suffixes are applied to an integer
|
| 14 |
resulting `chrono::duration` value cannot be represented in the result
|
| 15 |
type because of overflow, the program is ill-formed.
|
| 16 |
|
| 17 |
[*Example 1*:
|
| 18 |
|
|
|
|
| 1 |
+
### Suffixes for duration literals <a id="time.duration.literals">[[time.duration.literals]]</a>
|
| 2 |
|
| 3 |
+
This subclause describes literal suffixes for constructing duration
|
| 4 |
literals. The suffixes `h`, `min`, `s`, `ms`, `us`, `ns` denote duration
|
| 5 |
values of the corresponding types `hours`, `minutes`, `seconds`,
|
| 6 |
`milliseconds`, `microseconds`, and `nanoseconds` respectively if they
|
| 7 |
+
are applied to *integer-literal*s.
|
| 8 |
|
| 9 |
+
If any of these suffixes are applied to a *floating-point-literal* the
|
| 10 |
result is a `chrono::duration` literal with an unspecified
|
| 11 |
floating-point representation.
|
| 12 |
|
| 13 |
+
If any of these suffixes are applied to an *integer-literal* and the
|
| 14 |
resulting `chrono::duration` value cannot be represented in the result
|
| 15 |
type because of overflow, the program is ill-formed.
|
| 16 |
|
| 17 |
[*Example 1*:
|
| 18 |
|