std::uninit...t_construct(3)

πŸ“¦ version 2024.07.05, in nixpkgs unstable, opensuse-leap 16.0

πŸŽ€ NAME πŸŽ€

std::uninitialized_default_construct - std::uninitialized_default_construct

okay bestie, you're looking at the std::uninit...t_construct(3) page from the C++ Standard Libary manual β€” manual name folded in right here like a little name tag 🫢. It's giving full C++ standard-library realness, and we're gonna walk through every single detail together, no skips, no cap.


🌸 Synopsis 🌸

Defined in header <memory>

template< class ForwardIt >
void uninitialized_default_construct( ForwardIt first, ForwardIt last );  (1) (since C++17)

template< class ExecutionPolicy, class ForwardIt >
void uninitialized_default_construct( ExecutionPolicy&& policy,
                                      ForwardIt first, ForwardIt last );  (2) (since C++17)
  1. Constructs objects of type typename std::iterator_traits<ForwardIt>::value_type in the uninitialized storage designated by the range [first, last) by default-initialization, as if by:
for (; first != last; ++first)
    ::new (static_cast<void*>(std::addressof(*first)))
        typename std::iterator_traits<ForwardIt>::value_type;

If an exception is thrown during the initialization, the objects already constructed are destroyed in an unspecified order. unspecified order, bestie β€” don't go assuming anything fancy πŸ’€

  1. Same as (1), but executed according to policy. This overload participates in overload resolution only if std::is_execution_policy_v<std::decay_t<ExecutionPolicy>> is true. (until C++20)

std::is_execution_policy_v<std::remove_cvref_t<ExecutionPolicy>> is true. (since C++20)


✨ Parameters ✨

  • first, last β€” the range of the elements to initialize.
  • policy β€” the execution policy to use. See execution policy for details.

πŸ¦‹ Type requirements πŸ¦‹

  • ForwardIt must meet the requirements of LegacyForwardIterator.
  • No increment, assignment, comparison, or indirection through valid instances of ForwardIt may throw exceptions.

πŸŽ€ Return value πŸŽ€

(none)

literally nothing comes back β€” it's a void situation, and that's iconic πŸ’…


🌈 Complexity 🌈

Linear in the distance between first and last.


πŸ”₯ Exceptions πŸ”₯

The overload with a template parameter named ExecutionPolicy reports errors as follows:

  • If execution of a function invoked as part of the algorithm throws an exception and ExecutionPolicy is one of the standard policies, std::terminate is called. For any other ExecutionPolicy, the behavior is implementation-defined.
  • If the algorithm fails to allocate memory, std::bad_alloc is thrown.

🧚 Possible implementation 🧚

Here's how it could look under the hood β€” exact code, no cap:

template<class ForwardIt>
void uninitialized_default_construct(ForwardIt first, ForwardIt last)
{
    using Value = typename std::iterator_traits<ForwardIt>::value_type;
    ForwardIt current = first;
    try
    {
        for (; current != last; ++current)
        {
            ::new (const_cast<void*>(static_cast<const volatile void*>(
                std::addressof(*current)))) Value;
        }
    }
    catch (...)
    {
        std::destroy(first, current);
        throw;
    }
}

🌸 Example 🌸

Run this code, bestie β€” it's literally right here:

#include <cstring>
#include <iostream>
#include <memory>
#include <string>

struct S
{
    std::string m{"Default value"};
};

int main()
{
    constexpr int n{3};
    alignas(alignof(S)) unsigned char mem[n * sizeof(S)];

    try
    {
        auto first{reinterpret_cast<S*>(mem)};
        auto last{first + n};

        std::uninitialized_default_construct(first, last);

        for (auto it{first}; it != last; ++it)
            std::cout << it->m << '\n';

        std::destroy(first, last);
    }
    catch (...)
    {
        std::cout << "Exception!\n";
    }

    // Notice that for "trivial types" the uninitialized_default_construct
    // generally does not zero-fill the given uninitialized memory area.
    int v[]{1, 2, 3, 4};
    const int original[]{1, 2, 3, 4};
    std::uninitialized_default_construct(std::begin(v), std::end(v));

    // Maybe undefined behavior, pending CWG 1997.
    // for (const int i : v)
    //     std::cout << i << ' ';

    // The result is unspecified.
    std::cout <<
        (std::memcmp(v, original, sizeof(v)) == 0 ? "Unmodified\n" : "Modified\n");
}

⭐ Possible output ⭐

Default value
Default value
Default value
Unmodified

πŸ’€ Defect reports πŸ’€

The following behavior-changing defect reports were applied retroactively to previously published C++ standards.

  • LWG 3870 β€” applied to: C++20; behavior as published: this algorithm might create objects on a const storage; correct behavior: kept disallowed.

πŸ‘‘ See also πŸ‘‘

  • uninitialized_default_construct_n (C++17) β€” constructs objects by default-initialization in an uninitialized area of memory, defined by a start and a count (function template)
  • uninitialized_value_construct (C++17) β€” constructs objects by value-initialization in an uninitialized area of memory, defined by a range (function template)
  • ranges::uninitialized_default_construct (C++20) β€” constructs objects by default-initialization in an uninitialized area of memory, defined by a range (niebloid)

okay that's the whole page, bestie! source/version/date sign-off: http://cppreference.com, 2024.06.10, and the page is std::uninit...t_construct(3) β€” slay πŸ’–βœ¨

πŸ“¦ where this page comes from