std::inout_...:inout_ptr_t(3)

💅 std::inout_ptr_t::inout_ptr_t 💅

okay bestie so this is straight out of the C++ Standard Library manual, page std::inout_...:inout_ptr_t(3), and it's literally the constructor page for std::inout_ptr_t::inout_ptr_t. we're doing constructor lore today 🫶

✨ NAME ✨

std::inout_ptr_t::inout_ptr_t — yes it's the same name twice, that's not a typo, that's just how constructors are built 💀 it's the constructor, of inout_ptr_t, named inout_ptr_t. iconic behavior honestly.

🌸 Synopsis 🌸

explicit inout_ptr_t( Smart &sp, Args... args ); (1) (since C++23)
inout_ptr_t( const inout_ptr_t& ) = delete;      (2) (since C++23)

okay so what do these two actually do, let me break it down fr fr:

1. so this one creates an inout_ptr_t. it adapts sp as if it binds it to the Smart& member, then captures every argument t in args... as if it initializes the corresponding member of type T in Args... with std::forward<T>(t), and then it initializes the stored Pointer with sp if Smart is a pointer type — otherwise it initializes it with sp.get(). and bestie listen, sp.release() may be called if Smart is not a pointer type, and in that case it will not be called again inside the destructor. noted. 📝
2. the copy constructor is explicitly deleted. inout_ptr_t is neither copyable nor movable. she does not get copied, she does not get moved, she simply is. main character energy only 👑

---

🎀 Parameters 🎀

• sp — the object (typically a smart pointer) to adapt 💖
• args... — the arguments used for resetting to capture

🦋 Return value 🦋

(none) — yeah, nothing, nada, she's a constructor, she returns vibes only ✨

🔥 Exceptions 🔥

may throw implementation-defined exceptions. so like, don't assume she's always chill 😭

💜 Notes 💜

so if Smart is not a pointer type and sp.release() is not called by the constructor, it may be called by the destructor before resetting sp. keep that in mind bestie.

every argument in args... is moved into the created inout_ptr_t if it is of an object type, or transferred into the created inout_ptr_t as-is if it is of a reference type. two different lanes, same destination 🚗

🚨 and here's the one that matters: the constructor of inout_ptr_t is allowed to throw exceptions. for example, when sp is an intrusive pointer with a control block, the allocation for the new control block may be performed within the constructor rather than the destructor. so like, the throwing can happen earlier than u expected, no cap.

🌈 Example 🌈

This section is incomplete

Reason: no example

like, she's gorgeous but she's got no outfit pics yet 🙈

⭐ Category ⭐

• Todo no example

---

and that's the whole page fr fr 💖 this was std::inout_...:inout_ptr_t(3) from the cppreference vibes, served up 2024.06.10 — go off and construct responsibly bestie 🎀✨💅