16 Library introduction [library]

16.4 Method of description [description]

16.4.2 Other conventions [conventions]

16.4.2.2 Type descriptions [type.descriptions]

16.4.2.2.1 General [type.descriptions.general]

The Requirements subclauses may describe names that are used to specify constraints on template arguments.156

These names are used in library Clauses to describe the types that may be supplied as arguments by a C++ program when instantiating template components from the library.

Certain types defined in [input.output] are used to describe implementation-defined types.

They are based on other types, but with added constraints.

156)

Examples from [utility.requirements] include: Cpp17EqualityComparable, Cpp17LessThanComparable, Cpp17CopyConstructible.

Examples from [iterator.requirements] include: Cpp17InputIterator, Cpp17ForwardIterator.

⮥

16.4.2.2.2 Exposition-only types [expos.only.types]

Several types defined in [support] through [thread] and [depr] are defined for the purpose of exposition.

The declaration of such a type is followed by a comment ending in exposition only.

[ Example

namespace std {
  extern "C" using some-handler = int(int, void*, double);  // exposition only
}

The type placeholder some-handler can now be used to specify a function that takes a callback parameter with C language linkage.

— end example

]

16.4.2.2.3 Enumerated types [enumerated.types]

Several types defined in [input.output] are enumerated types.

Each enumerated type may be implemented as an enumeration or as a synonym for an enumeration.157

The enumerated type enumerated can be written:

enum enumerated {  $V_{0}$ ,  $V_{1}$ ,  $V_{2}$ ,  $V_{3}$ , … };

inline const  ${enumerated C}_{0}$ ( $V_{0}$ );
inline const  ${enumerated C}_{1}$ ( $V_{1}$ );
inline const  ${enumerated C}_{2}$ ( $V_{2}$ );
inline const  ${enumerated C}_{3}$ ( $V_{3}$ );
  ⋮

Here, the names

C_{0}

C_{1}

, etc. represent enumerated elements for this particular enumerated type.

All such elements have distinct values.

157)

Such as an integer type, with constant integer values ([basic.fundamental]).

⮥

16.4.2.2.4 Bitmask types [bitmask.types]

Several types defined in [support] through [thread] and [depr] are bitmask types.

Each bitmask type can be implemented as an enumerated type that overloads certain operators, as an integer type, or as a bitset .

The bitmask type bitmask can be written:

// For exposition only.
// int_type is an integral type capable of representing all values of the bitmask type.
enum bitmask : int_type {
   $V_{0}$  = 1 << 0,  $V_{1}$  = 1 << 1,  $V_{2}$  = 1 << 2,  $V_{3}$  = 1 << 3, …
};

inline constexpr  ${bitmask C}_{0}$ ( $V_{0}$ );
inline constexpr  ${bitmask C}_{1}$ ( $V_{1}$ );
inline constexpr  ${bitmask C}_{2}$ ( $V_{2}$ );
inline constexpr  ${bitmask C}_{3}$ ( $V_{3}$ );
  ⋮

constexpr bitmask operator&(bitmask X, bitmask Y) {
  return static_cast<bitmask>(
    static_cast<int_type>(X) & static_cast<int_type>(Y));
}
constexpr bitmask operator|(bitmask X, bitmask Y) {
  return static_cast<bitmask>(
    static_cast<int_type>(X) | static_cast<int_type>(Y));
}
constexpr bitmask operator^(bitmask X, bitmask Y){
  return static_cast<bitmask>(
    static_cast<int_type>(X) ^ static_cast<int_type>(Y));
}
constexpr bitmask operator~(bitmask X){
  return static_cast<bitmask>(~static_cast<int_type>(X));
}
bitmask& operator&=(bitmask& X, bitmask Y){
  X = X & Y; return X;
}
bitmask& operator|=(bitmask& X, bitmask Y) {
  X = X | Y; return X;
}
bitmask& operator^=(bitmask& X, bitmask Y) {
  X = X ^ Y; return X;
}

Here, the names

C_{0}

C_{1}

, etc. represent bitmask elements for this particular bitmask type.

All such elements have distinct, nonzero values such that, for any pair

C_{i}

and

C_{j}

where

i \neq j

C_{i}

C_{i}

is nonzero and

C_{i}

C_{j}

is zero.

Additionally, the value 0 is used to represent an empty bitmask, in which no bitmask elements are set.

The following terms apply to objects and values of bitmask types:

(4.1)
To set a value Y in an object X is to evaluate the expression X |= Y.
(4.2)
To clear a value Y in an object X is to evaluate the expression X &= ~Y.
(4.3)
The value Y is set in the object X if the expression X & Y is nonzero.

16.4.2.2.5 Character sequences [character.seq]

The C standard library makes widespread use of characters and character sequences that follow a few uniform conventions:

(1.1)
A letter is any of the 26 lowercase or 26 uppercase letters in the basic execution character set.
(1.2)
The decimal-point character is the (single-byte) character used by functions that convert between a (single-byte) character sequence and a value of one of the floating-point types.

It is used in the character sequence to denote the beginning of a fractional part.

It is represented in [support] through [thread] and [depr] by a period, '.', which is also its value in the "C" locale, but may change during program execution by a call to setlocale(int, const char*),158 or by a change to a locale object, as described in [locales] and [input.output].
(1.3)
A character sequence is an array object A that can be declared as T A[N], where T is any of the types char, unsigned char, or signed char ([basic.fundamental]), optionally qualified by any combination of const or volatile.

The initial elements of the array have defined contents up to and including an element determined by some predicate.

A character sequence can be designated by a pointer value S that points to its first element.

158)

declared in <clocale> ([clocale.syn]).

⮥

16.4.2.2.5.1 Byte strings [byte.strings]

A null-terminated byte string, or ntbs, is a character sequence whose highest-addressed element with defined content has the value zero (the terminating null character); no other element in the sequence has the value zero.159

The length of an ntbs is the number of elements that precede the terminating null character.

An empty ntbs has a length of zero.

The value of an ntbs is the sequence of values of the elements up to and including the terminating null character.

A static ntbs is an ntbs with static storage duration.160

159)

Many of the objects manipulated by function signatures declared in <cstring> ([cstring.syn]) are character sequences or ntbss.

The size of some of these character sequences is limited by a length value, maintained separately from the character sequence.

⮥

160)

A string-literal, such as "abc", is a static ntbs.

⮥

16.4.2.2.5.2 Multibyte strings [multibyte.strings]

A null-terminated multibyte string, or ntmbs, is an ntbs that constitutes a sequence of valid multibyte characters, beginning and ending in the initial shift state.161

A static ntmbs is an ntmbs with static storage duration.

161)

An ntbs that contains characters only from the basic execution character set is also an ntmbs.

Each multibyte character then consists of a single byte.

⮥

16.4.2.2.6 Customization Point Object types [customization.point.object]

A customization point object is a function object ([function.objects]) with a literal class type that interacts with program-defined types while enforcing semantic requirements on that interaction.

The type of a customization point object, ignoring cv-qualifiers, shall model semiregular ([concepts.object]).

All instances of a specific customization point object type shall be equal ([concepts.equality]).

The type T of a customization point object shall model invocable<const T&, Args...> ([concept.invocable]) when the types in Args... meet the requirements specified in that customization point object's definition.

When the types of Args... do not meet the customization point object's requirements, T shall not have a function call operator that participates in overload resolution.

Each customization point object type constrains its return type to model a particular concept.

[ Note

Many of the customization point objects in the library evaluate function call expressions with an unqualified name which results in a call to a program-defined function found by argument dependent name lookup ([basic.lookup.argdep]).

To preclude such an expression resulting in a call to unconstrained functions with the same name in namespace std, customization point objects specify that lookup for these expressions is performed in a context that includes deleted overloads matching the signatures of overloads defined in namespace std.

When the deleted overloads are viable, program-defined overloads need be more specialized ([temp.func.order]) or more constrained ([temp.constr.order]) to be used by a customization point object.

— end note

]