We're both from the future!

Understanding std::future lifecycle and scope behavior in C++

This is a medium-difficulty concurrency question that tests your understanding of how std::future objects behave when they are destroyed—specifically, what happens to the underlying asynchronous task and shared state when a future falls out of scope. The question requires you to reason about the relationship between futures and their associated tasks, and the guarantees (or lack thereof) that the standard provides.

To approach this correctly, you need to distinguish between the future object itself and the asynchronous work it represents. Key considerations include whether a future blocks on destruction, whether it abandons the task, and how the shared state—the bridge between the async task and the future—affects that behavior. This is particularly important in systems where thread lifetime and resource cleanup matter.

• Shared state and task lifecycle
• Blocking vs. non-blocking destruction semantics
• The role of std::async launch policies
• When a future must wait for completion