C++ Standard Library
The C++ standard library provides a wide range of facilities that are usable in standard C++.
The general utilities library includes components used by other library elements, such as a predefined storage allocator for dynamic storage management, and components used as infrastructure in C++ programs, such as tuples and (since C++11) function wrappers.
The strings library provides support for manipulating text represented as homogeneous sequences of following types: char, char8_t (since C++20), char16_t, char32_t (since C++11), wchar_t, and any other character-like types.
The numerics library provides numeric algorithms and complex number components that extend support for numeric processing. The valarray component provides support for n-at-a-time processing, potentially implemented as parallel operations on platforms that support such processing. The random number component provides facilities for generating pseudo-random numbers. (since C++11)
The time library provides generally useful time utilities.
The localization library provides extended internationalization support for text processing.
The input/output library provides the iostream components that are the primary mechanism for C++ program input and output. They can be used with other elements of the library, particularly strings, locales, and iterators.
The regular expressions library provides regular expression matching and searching.
 Library contents
All library entities except operator new and operator delete are defined within the namespace std or namespaces nested within namespace std (except the entities for the C standard library facilities, see below). It is unspecified whether names declared in a specific namespace are declared directly in that namespace or in an inline namespace inside that namespace. (since C++11)
Each element of the C++ standard library is declared or defined (as appropriate) in a header. A header is not necessarily a source file, nor are the sequences delimited by < and > in header names necessarily valid source file names.
The C++ standard library provides the C++ library headers and additional C++ headers for C library facilities (see 'headers' page for descriptions):
|C++ headers for C library facilities|
|Headers removed in C++20|
|Headers added in C++11|
|Headers added in C++11, deprecated in C++17, and removed in C++20|
 C standard library
The C++ standard library also makes available the facilities of the C standard library, suitably adjusted to ensure static type safety. The descriptions of many library functions rely on the C standard library for the semantics of those functions.
In some cases, the signatures specified in standard C++ may be different from the signatures in the C standard library, and additional overloads may be declared, but the behavior and the preconditions (including those implied by C's restrict) (since C++17) are the same unless otherwise stated.
For compatibility with the C standard library, the C++ standard library provides the C headers listed below. The intended use of these headers is for interoperability only. It is possible that C++ source files need to include one of these headers in order to be valid ISO C. Source files that are not intended to also be valid ISO C should not use any of the C headers. See here for descriptions.
|Headers added in C++11|
|Headers added in C++23|
Except otherwise noted, the contents of each header
cxxx is the same as that of the corresponding header
xxx.h as specified in the C standard library. In the C++ standard library, however, the declarations (except for names which are defined as macros in C) are within namespace scope of the namespace std. It is unspecified whether these names (including any overloads added) are first declared within the global namespace scope and are then injected into namespace std by explicit using-declarations.
Names which are defined as macros in C (assert, offsetof, setjmp, va_arg, va_end and va_start) must be defined as macros in the C++ standard library, even if C grants license for implementation as functions.
Names that are defined as functions in C must be defined as functions in the C++ standard library. This disallows the practice, allowed in C, of providing a masking macro in addition to the function prototype. The only way to achieve equivalent inline behavior in C++ is to provide a definition as an extern inline function.
Identifiers that are keywords or operators in C++ cannot be defined as macros in C++ standard library headers. In particular, including the standard header <iso646.h> has no effect.
 Names associated with safe functions in standard C (since C++17)
If any C++ header is included, it is implementation-defined whether any of the following C standard Annex K names is declared in the global namespace (none of them is declared in namespace std):
 Using the library
 Including headers
The entities in the C++ standard library are defined in headers, whose contents are made available to a translation unit when it contains the appropriate #include preprocessing directive.
A translation unit may include library headers in any order. Each may be included more than once, with no effect different from being included exactly once, except that the effect of including either <cassert> or <assert.h> depends each time on the lexically current definition of NDEBUG.
A translation unit can only include a header outside of any declaration or definition, and lexically before the first reference in that translation unit to any of the entities declared in that header. No diagnostic is required.
The C++ library headers, or, for a freestanding implementation, the subset of such headers that are provided by the implementation, are collectively known as the importable C++ library headers .
The contents of importable C++ library headers are made available to a translation unit when it contains the appropriate import declaration.
The C++ standard library provides the following C++ library modules:
For each declaration in the standard library,
Whether a name from the C standard library declared with external linkage has extern "C" or extern "C++" linkage is implementation-defined. The C++ standard recommends using extern "C++" in this case.
Objects and functions defined in the library and required by a C++ program are included in the program prior to program startup.
 Requirements on standard library implementations
- the synopsis of that header, or
- the synopsis of another header which is appeared to be included in the synopsis of that header.
Calling a standard library non-member function signature always results in actually calling that function. Therefore a conforming standard library implementation cannot define additional non-member functions that may be called by a valid C++ program.
Non-member function signatures are never declared with additional default arguments.
Unless otherwise specified, calls made by functions in the standard library to non-operator, non-member functions do not use functions from another namespace which are found through argument-dependent name lookup.
For each friend declaration of a function (template) within a class (template) definition, no other declaration is provided for that function (template).
Standard library function signatures can only be declared as constexpr if they are required to be constexpr (libstdc++ cmath is notably non-conforming here). If a header provides any non-defining declarations of constexpr functions or constructors, the corresponding definitions should also be provided within that header.
Unless otherwise specified, each standard library function should meet each of the following requirements to prevent data races:
For each class defined in the C++ standard library required to be derived from another class defined in the C++ standard library,
- the base class must be virtual if it is specified as virtual,
- the base class cannot be virtual if it is not specified as virtual, and
- unless otherwise specified, types with distinct names shall be distinct types.
Unless otherwise specified, all types specified in the C++ standard library are non-final types.
If a function defined in the C++ standard library is specified to throw an exception (in a particular situation) of a given type, the exception thrown can only have that type or a type derived from that type so that an exception handler for the base type can catch it.
Destructor operations defined in the C++ standard library never throw exceptions. Every destructor in the C++ standard library behaves as if it had a non-throwing exception specification.
If a function in the C++ standard library report errors via a std::error_code object, that object's category() member must return std::system_category() for errors originating from the operating system, or a reference to an implementation-defined std::error_category object for errors originating elsewhere. The possible values of value() for each of these error categories should be defined.
Objects of types defined in the C++ standard library may be moved from. Move operations can either be explicitly specified or implicitly generated. Unless otherwise specified, such moved-from objects will be placed in a valid but unspecified state.
An object of a type defined in the C++ standard library may be move-assigned to itself. Unless otherwise specified, such an assignment places the object in a valid but unspecified state.
 Implementation freedom
It is unspecified whether any member or non-member functions in the C++ standard library are defined as inline.
For a non-virtual C++ standard library member function, a different set of member function signatures can be declared, provided that any call to that member function that would select an overload from the given set of declarations behaves as if that overload was selected. This allows, for instance:
- adding parameters with default arguments,
- replacing a member function with default arguments with two or more member functions with equivalent behavior, or
- adding additional signatures for a member function name.
Unless otherwise specified, it is implementation-defined which functions in the C++ standard library may be recursively reentered.
C++ standard library implementations can share their own internal objects between threads if the objects are not visible to users and are protected against data races.
It is unspecified whether any function signature or class in the C++ standard library is a friend of another class in the C++ standard library.
The names and global function signatures described here are reserved to the implementation.
Any class in the C++ standard library can be derived from a class with a name reserved to the implementation. If a class defined in the C++ standard library is required to be derived from other classes in the C++ standard library, that class can be derived directly from the required base or indirectly through a hierarchy of base classes with names reserved to the implementation.
If a function defined in the C++ standard library is not specified to throw an exception but does not have a non-throwing exception specification, the exception thrown is implementation-defined, but its type should be std::exception or any type derived from std::exception.
The exception specification for a non-virtual function can be strengthened by adding a non-throwing exception specification.
 Defect reports
The following behavior-changing defect reports were applied retroactively to previously published C++ standards.
|DR||Applied to||Behavior as published||Correct behavior|
|LWG 1||C++98|| the language linkages of the names from
the C standard library were unspecified
| they are|
|LWG 119||C++98|| the exception specifications of virtual
functions could be strengthened
| only allowed for|
|LWG 147||C++98|| the specification on non-member
functions only considered global functions
| also considers|
|LWG 225||C++98|| standard library functions might call non-member functions
from other namespaces due to argument-dependent lookup
| prohibited unless|
|LWG 336||C++98||<strstream> was not a C++ library header||it is a C++ library header|
|LWG 343||C++98||library header dependencies were not specified||specified (listed in synopses)|
|LWG 456||C++98|| C++ headers for C library facilities could
only provide definitions in namespace std
| allowed to define in global namespace|
and then inject into namespace std
|LWG 465||C++98|| identifiers that are keywords or operators in C++ could
be defined as macros in C++ standard library headers
(only <ciso646> is required not to define them as macros)
| all C++ standard|
library headers cannot
define them as macros
|LWG 1178||C++98|| C++ headers must include a C++ header
that contains any needed definition
| C++ headers must provide declarations|
and definitions that are directly or
indirectly included in its synopsis
|LWG 2013||C++11|| it was unspecified whether the functions not
required by the standard to be constexpr can
be declared constexpr by the standard library