std::bad_alloc(3)

💖 NAME 💖

std::bad_alloc — the exception that new might just throw at you, bestie. No cap.

---

✨ SYNOPSIS ✨

#include <new_except.h>

She inherits from std::exception. Classic family tree moment.

🎀 Public Member Functions

_GLIBCXX26_CONSTEXPR bad_alloc (const bad_alloc &)=default
_GLIBCXX26_CONSTEXPR bad_alloc & operator= (const bad_alloc &)=default
virtual constexpr const char * what () const noexcept

---

🌸 Detailed Description 🌸

Okay so, real talk: std::bad_alloc is the exception that new possibly throws. Emphasis on possibly — she's not committing to anything, she's just saying it's on the table.

bad_alloc — or any of the classes derived from it, because the whole girlies family is welcome — is what gets used to report allocation errors coming from the throwing forms of new. Like, if you asked new for memory and new couldn't deliver, this is the notification you get. It's giving "we need to talk." 😭

---

💅 Member Function Documentation 💅

virtual constexpr const char * std::bad_alloc::what () const [inline], [constexpr], [virtual], [noexcept]

THE girl. 🌈

She returns a C-style character string that describes the general cause of the current error. That's it, that's the job — a little const char * telling you what went wrong in the vaguest possible way. 👑

Reimplemented from std::exception. So yeah, she's over here doing her own version of the family classic.

---

🦋 Author 🦋

Generated automatically by Doxygen for libstdc++ from the source code. So nobody hand-wrote this one, she simply materialised. Main character behaviour fr fr. ✨

---

Okay bestie, that's the whole page! It's from the libstdc++ library and the footer is literally just the word libstdc++ (Library Functions Manual energy), and as for the date… she left it blank, iconic, she's timeless. 🫶 Mwah, go catch that exception. 💖