Exit Zen
11
:28
English
small strings.
6/140 · 14
12
:30
English
With augmented interface, operations requiring an input string are implemented as a single overload with a parameter of type <<ref_string_view>>, and can accept most string-like objects. Objects such as null terminated character pointers, `std::string`, <<ref_string>>, subranges of strings, and objects convertible to <<ref_string_view>> can all be passed to these functions.
229/3760 · 376
13
:41
English
More formally, `std::string` member function overloads that accept any of the following parameter combinations as an input string:
46/1300 · 130
14
:44
English
a `std::string` parameter, or
19/290 · 29
15
:45
English
a `std::string` parameter and two `size_type` parameters that specify a
53/710 · 71
16
:46
English
substring, or
6/130 · 13
17
:47
English
a parameter of a type convertible to <<ref_string_view>>, or
58/600 · 60
18
:48
English
a parameter of a type convertible to <<ref_string_view>> and two
60/640 · 64
19
:49
English
`size_type` parameters that specify a substring, or
28/510 · 51
20
:50
English
a `const_pointer` parameter, or
21/310 · 31
21
:51
English
a parameter of type `const_pointer` and a `size_type` parameter that
44/680 · 68
22
:52
English
specifies the length of the string
9/340 · 34
23
:54
English
are replaced with an overload accepting a <<ref_string_view>> parameter.
59/720 · 72
24
:56
English
This design removes several redundant overloads from the interface. For example, the 11 overloads of `std::string::insert` are reduced to just 3 in <<ref_string>>, while still providing identical functionality. In addition to these changes, overloads taking a `std::initializer_list<char>` parameter have been removed. Such overloads have little use, as they serve as little more than wrappers for arrays with an inefficient syntax:
206/4320 · 432
25
:68
English
With the removal of overloads that specify parameters for a substring, a member function `subview` that returns a <<ref_string_view>> is provided to facilitate cheap substring operations:
105/1870 · 187
26
:77
English
A <<ref_string>> may be constructed using the <<default_memory_resource,default memory resource>> without incurring any memory allocations. Alternatively, a <<ref_storage_ptr>> can be provided explicitly:
218/2040 · 204
27
:86
English
Formatted Output
5/160 · 16
28
:88
English
When a <<ref_string>> is formatted to a {std_ostream}, the result is a valid JSON. That is, the result will be double quoted and the contents properly escaped per the JSON specification.
101/1860 · 186
29
:92
English
Accessing Storage Beyond `size()`
19/330 · 33
30
:94
English
<<ref_string>> directly supports access to its storage in the range `[size(), capacity())`. This can be used for efficient assembly of a string from several parts. After the string is assembled, use the member function <<ref_string_grow>> to update the string's size and insert the null terminator. For example:
175/3110 · 311
The translation has come to an end.