std::packag...ckaged_task(3)

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

πŸ’– NAME πŸ’–

std::packaged_task::~packaged_task - std::packaged_task::~packaged_task

Hiii bestie!! 🫢 This is the C++ Standard Libary corner of the group chat (yes, that's the manual name, spelling and all β€” no cap, I'm not touching it πŸ’…), and today's page is std::packag...ckaged_task(3). Main character: the destructor for std::packaged_task. It's giving cleanup era. ✨


🌸 Synopsis 🌸

~packaged_task();

Okay so ~packaged_task(); abandons the shared state and destroys the stored task object. That's the whole vibe check. 🧹

And listen, bestie: as with std::promise::~promise, if the shared state is abandoned before it was made ready, an std::future_error exception is stored with the error code std::future_errc::broken_promise). So the promise is literally broken, and the error code is right there living its truth. πŸ’€ That trailing ) is literally in the error-code text, so I'm keeping it exactly. No editing the source, periodt.

πŸŽ€ Parameters πŸŽ€

(none)

No parameters, bestie. Zero. Nada. The function is booked, busy, and parameter-free. πŸŽ€

πŸ¦‹ Example πŸ¦‹

This section is incomplete Reason: no example

The example section is lowkey crying in the club 😭 β€” no example yet. We still love her.

🌈 Category: 🌈

  • Todo no example

Sign-off vibes: source/version/date are http://cppreference.com, 2024.06.10, and std::packag...ckaged_task(3). Mwah πŸ’‹ stay slay, bestie! 🫢

πŸ“¦ where this page comes from