std::future::~future(3)
β¨ NAME β¨
std::future::~future - std::future::~future
okay so youβre on the std::future::~future(3) page in the C++ Standard Libary manual, bestie. Yes, the NAME line is literally the same thing twice β itβs giving βI am my own iconβ energy. π
π Synopsis π
~future(); (since C++11)
Destructor szn. It releases any shared state. This means:
- if the current object holds the last reference to its shared state, the shared state is destroyed;
- the current object gives up its reference to its shared state;
- these actions will not block for the shared state to become ready, except that they may block if all of the following are true:
- the shared state was created by a call to
std::async(since C++14) - the shared state is not yet ready, and
- the current object was the last reference to the shared state.
- the shared state was created by a call to
In practice, these actions will block only if the taskβs launch policy is std::launch::async (see "Effective Modern C++" Item 36), either because that was chosen by the runtime system or because it was specified in the call to std::async. π«Ά
source: http://cppreference.com Β· version/date: 2024.06.10 Β· page: std::future::~future(3) β¨π
π¦ where this page comes from
- nixpkgs unstable: stdman 2024.07.05
- opensuse-leap 16.0: stdman 2024.07.05-bp160.1.9 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms