On Saturday 17 August 2013 20:48:49 Oliver Kowalke wrote:
2013/8/17 Andrey Semashev
You can use future and promise to pass asynchronous values, true. But still, its primary use is with threads. Things like async() and future.then() use threads to carry out actions. Even if you don't use these features, you can still use futures from Boost.Thread.
I mean using fibers instead threads
You can't safely use regular mutexes and condition variables with fibers, can you? If you block, you won't switch to another fiber, which you may be waiting for.
Note that I'm not saying there's no point in loosening this dependency of futures on threads. I'm saying that Boost.Sync doesn't look like a proper place for futures.
maybe boost.future?
Maybe. That's along the lines of the Boost.Async suggestion.