You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/standard-library/charconv-functions.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -13,13 +13,13 @@ The \<charconv> header includes the following non-member functions:
13
13
|[to_chars](#to_chars)| Convert an integer or floating-point value to a sequence of **`char`**. |
14
14
|[from_chars](#from_chars)| Convert a sequence of **`char`** to an integer or floating-point value. |
15
15
16
-
These conversion functions are tuned for performance, and also support shortest-round-trip behavior. Shortest-round-trip behavior means that when a number is converted to chars, only enough precision is written out to enable recovering the original number when converting those chars back to a floating-point.
16
+
These conversion functions are tuned for performance, and also support shortestround-trip behavior. Shortestround-trip behavior means when a number is converted to chars, only enough precision is written out to enable recovering the original number when converting those chars back to a floating-point.
17
17
18
-
- When converting chars to a number, the numeric value does not need to be null-terminated. Likewise, when converting a number to chars, the result is not null-terminated.
18
+
- When converting chars to a number, the numeric value doesn't need to be null-terminated. Likewise, when converting a number to chars, the result isn't null-terminated.
19
19
- The conversion functions don't allocate memory. You own the buffer in all cases.
20
20
- The conversion functions don't throw. A result is returned from which you can determine if the conversion succeeded.
21
-
- The conversion functions are not runtime rounding-mode sensitive.
22
-
- The conversion functions are not locale aware. They always print and parse decimal points as `'.'`, and never as ',' for locales that use commas.
21
+
- The conversion functions aren't runtime rounding-mode sensitive.
22
+
- The conversion functions aren't locale aware. They always print and parse decimal points as `'.'`, and never as ',' for locales that use commas.
23
23
24
24
## `to_chars`
25
25
@@ -89,7 +89,7 @@ A [to_chars_result](to-chars-result-structure.md) containing the result of the c
89
89
Functions taking a [chars_format](chars-format-class.md) parameter determine the conversion specifier as if they were using `printf()` as follows:
90
90
The conversion specifier is `'f'` if `fmt` is `chars_format::fixed`, `'e'` if `fmt` is `chars_format::scientific`, `'a'` (without the leading `0x` in the result) if `fmt` is `chars_format::hex`, and `'g'` if `fmt` is `chars_format::general`. Specifying the shortest fixed notation may still result in lengthy output because it may be the shortest possible representation when the value is very large or very small.
91
91
92
-
The following table describes the conversion behavior given different combinations of `fmt` and `precision` parameters. The term "shortest round-trip" refers to writing the fewest number of digits necessary such that parsing that representation using the corresponding `from_chars` function will recover the value exactly.
92
+
The following table describes the conversion behavior given different combinations of `fmt` and `precision` parameters. The term "shortest roundtrip" refers to writing the fewest number of digits necessary such that parsing that representation using the corresponding `from_chars` function will recover the value exactly.
0 commit comments