std::ranges...ialized_fill(3)

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

πŸ’– std::ranges::uninitialized_fill πŸ’–

okay so this is the std::ranges::uninitialized_fill page from the C++ Standard Libary manual β€” yes bestie, the header spells it std::ranges...ialized_fill(3) like a truncated group-chat nickname πŸ’€. No cap, we're getting into uninitialized memory and it's lowkey iconic.


🌸 NAME 🌸

std::ranges::uninitialized_fill β€” std::ranges::uninitialized_fill


✨ Synopsis ✨

Defined in header <memory>

Call signature:

template< no-throw-forward-iterator I, no-throw-sentinel-for<I> S, class T >
    (1)
    (since C++20)
requires std::constructible_from<std::iter_value_t<I>, const T&>
I uninitialized_fill( I first, S last, const T& x );

template< no-throw-forward-range R, class T >
    (2)
    (since C++20)
requires std::constructible_from<ranges::range_value_t<R>, const T&>
ranges::borrowed_iterator_t<R>
uninitialized_fill( R&& r, const T& x );

1) Constructs N copies of the given value x in an uninitialized memory area, designated by the range [first, last), where N is ranges::distance(first, last).

The function has the effect equivalent to:

for (; first != last; ++first)
    ::new (static_cast<void*>(std::addressof(*first)))
        std::remove_reference_t<std::iter_reference_t<I>>(x);
return first;

If an exception is thrown during the initialization, the objects already constructed are destroyed in an unspecified order. Important bestie β€” rollback vibes are real but the order is unspecified.

2) Same as (1), but uses r as the range, as if using ranges::begin(r) as first, and ranges::end(r) as last.

The function-like entities described on this page are niebloids, that is:

  • Explicit template argument lists cannot be specified when calling any of them.
  • None of them are visible to argument-dependent lookup.
  • When any of them are found by normal unqualified lookup as the name to the left of the function-call operator, argument-dependent lookup is inhibited.

In practice, they may be implemented as function objects, or with special compiler extensions.


πŸŽ€ Parameters πŸŽ€

  • first, last β€” iterator-sentinel pair denoting the range of elements to initialize.
  • r β€” the range of the elements to initialize.
  • value β€” the value to construct the elements with. (The signatures above call this arg x, iykyk β€” same energy, different label πŸ’…)

🫢 Return value 🫢

An iterator equal to last. Periodt.


πŸŒ€ Complexity πŸŒ€

\(\scriptsize\mathcal{O}(N)\)π“ž(N) β€” it's giving linear, bestie.


πŸ’€ Exceptions πŸ’€

The exception thrown on construction of the elements in the destination range, if any.


πŸ“ Notes πŸ“

An implementation may improve the efficiency of the ranges::uninitialized_fill, e.g. by using ranges::fill, if the value type of the output range is TrivialType. No cap β€” that's the whole note.


πŸ› οΈ Possible implementation πŸ› οΈ

struct uninitialized_fill_fn
{
    template<no-throw-forward-iterator I, no-throw-sentinel-for<I> S, class T>
    requires std::constructible_from<std::iter_value_t<I>, const T&>
    I operator()(I first, S last, const T& x) const
    {
        I rollback{first};
        try
        {
            for (; !(first == last); ++first)
                ranges::construct_at(std::addressof(*first), x);
            return first;
        }
        catch (...)
        {
            // rollback: destroy constructed elements
            for (; rollback != first; ++rollback)
                ranges::destroy_at(std::addressof(*rollback));
            throw;
        }
    }

    template<no-throw-forward-range R, class T>
    requires std::constructible_from<ranges::range_value_t<R>, const T&>
    ranges::borrowed_iterator_t<R>
    operator()(R&& r, const T& x) const
    {
        return (*this)(ranges::begin(r), ranges::end(r), x);
    }
};

inline constexpr uninitialized_fill_fn uninitialized_fill{};

🌈 Example 🌈

Run this code, bestie:

// Run this code
#include <iostream>
#include <memory>
#include <string>

int main()
{
    constexpr int n{4};
    alignas(alignof(std::string)) char out[n * sizeof(std::string)];

    try
    {
        auto first{reinterpret_cast<std::string*>(out)};
        auto last{first + n};
        std::ranges::uninitialized_fill(first, last, "β–„β–€β–„β–€β–„β–€β–„β–€");

        int count{1};
        for (auto it{first}; it != last; ++it)
            std::cout << count++ << ' ' << *it << '\n';

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

πŸ“ Output πŸ“

1 β–„β–€β–„β–€β–„β–€β–„β–€
2 β–„β–€β–„β–€β–„β–€β–„β–€
3 β–„β–€β–„β–€β–„β–€β–„β–€
4 β–„β–€β–„β–€β–„β–€β–„β–€

🧚 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 πŸ‘‘

  • ranges::uninitialized_fill_n (C++20) β€” copies an object to an uninitialized area of memory, defined by a start and a count (niebloid).
  • uninitialized_fill β€” copies an object to an uninitialized area of memory, defined by a range (function template).

mwah πŸ’‹ β€” sourced from http://cppreference.com, version/date 2024.06.10, and the page id is std::ranges...ialized_fill(3). Bye bestie, go fill some uninitialized memory responsibly! 🫢✨

πŸ“¦ where this page comes from