Futures vs. Promises

by

Future and Promise are the two separate sides of an asynchronous operation.

std::promise is used by the “producer/writer” of the asynchronous operation.

std::future is used by the “consumer/reader” of the asynchronous operation.

The reason it is separated into these two separate “interfaces” is to hide the “write/set” functionality from the “consumer/reader”.

auto promise = std::promise<std::string>();

auto producer = std::thread([&]
{
    promise.set_value("Hello World");
});

auto future = promise.get_future();

auto consumer = std::thread([&]
{
    std::cout << future.get();
});

producer.join();
consumer.join();

One (incomplete) way to implement std::async using std::promise could be:

template<typename F>
auto async(F&& func) -> std::future<decltype(func())>
{
    typedef decltype(func()) result_type;

    auto promise = std::promise<result_type>();
    auto future  = promise.get_future();

    std::thread(std::bind([=](std::promise<result_type>& promise)
    {
        try
        {
            promise.set_value(func()); // Note: Will not work with std::promise<void>. Needs some meta-template programming which is out of scope for this question.
        }
        catch(...)
        {
            promise.set_exception(std::current_exception());
        }
    }, std::move(promise))).detach();

    return std::move(future);
}

Using std::packaged_task which is a helper (i.e. it basically does what we were doing above) around std::promise you could do the following which is more complete and possibly faster:

template<typename F>
auto async(F&& func) -> std::future<decltype(func())>
{
    auto task   = std::packaged_task<decltype(func())()>(std::forward<F>(func));
    auto future = task.get_future();

    std::thread(std::move(task)).detach();

    return std::move(future);
}

Note that this is slightly different from std::async where the returned std::future will when destructed actually block until the thread is finished.

More Related Contents:

  1. Get the status of a std::future
  2. Is there a way to cancel/detach a future in C++11?
  3. Why should I use std::async?
  4. What is std::promise?
  5. What exactly is nullptr?
  6. Why don’t compilers merge redundant std::atomic writes?
  7. Copy constructor for a class with unique_ptr
  8. std::array vs array performance
  9. How to initialize std::array elegantly if T is not default constructible?
  10. lifetime of a std::initializer_list return value
  11. Brace-enclosed initializer list constructor
  12. Where can I use alignas() in C++11?
  13. Is it possible to determine if a type is a scoped enumeration type?
  14. Is there actually a reason why overloaded && and || don’t short circuit?
  15. std::thread is not a member of namespace std using Eclipse Kepler MinGW
  16. Which cannot be implemented without compiler hooks?
  17. Should I delete the move constructor and the move assignment of a smart pointer?
  18. What is the value category of the operands of C++ operators when unspecified?
  19. Concat two `const char` string literals
  20. Waiting for multiple futures?
  21. How do memory_order_seq_cst and memory_order_acq_rel differ?
  22. When to make a type non-movable in C++11?
  23. Why was std::pow(double, int) removed from C++11?
  24. MinGW error: ‘thread’ is not a member of ‘std’
  25. Why does unique_ptr take two template parameters when shared_ptr only takes one?
  26. Difference between steady_clock vs system_clock?
  27. Initialization difference with or without curly braces in C++
  28. Should std::unique_ptr be permitted
  29. Initializing an std::array of non-default-constructible elements?
  30. Does the C++ standard specify anything on the representation of floating point numbers?

Leave a Comment