std::alloca...ts::max_size(3)

✨ NAME ✨

okay so bestie, this is the std::alloca...ts::max_size(3) page from the C++ Standard Libary manual 💅 — and the NAME is literally std::allocator_traits::max_size — std::allocator_traits::max_size. yes, iconically redundant, we love that for us 🎀.

---

🌸 Synopsis 🌸

Defined in header <memory>:

static size_type max_size( const Alloc& a ) noexcept;

(since C++11) (until C++20)

static constexpr size_type max_size( const Alloc& a ) noexcept;

(since C++20)

So here's the tea ☕: if possible, this obtains the maximum theoretically possible allocation size from the allocator a, by calling a.max_size().

If the above is not possible — like, say, Alloc does not have the member function max_size() — then it returns std::numeric_limits<size_type>::max() / sizeof(value_type). no cap, that's the fallback 💫.

---

🎀 Parameters 🎀

• a — allocator to detect 🔍

---

🦋 Return value 🦋

Theoretical maximum allocation size. periodt 💅.

---

💅 Defect reports 💅

The following behavior-changing defect reports were applied retroactively to previously published C++ standards. yes, we're going back in time, main character energy 🕰️✨.

• LWG 2162, applied to C++11 — behavior as published: max_size was not “requied” to be noexcept (their spelling, not mine 😭); correct behavior: required.
• LWG 2466, applied to C++11 — behavior as published: the theoretical maximum allocation size in bytes was returned as the fallback; correct behavior: the size in elements is returned. slay for correctness 🌟.

---

🌈 See also 🌈

• max_size — returns the largest supported allocation size (until C++20) (public member function of std::allocator<T>) 👑

---

okay that's the whole vibe 💖 — footer tea: this page is from http://cppreference.com, version date 2024.06.10, and the page tag is std::alloca...ts::max_size(3). mwah 💋✨