11 Mar
2007
11 Mar
'07
5:05 p.m.
Braddock Gaskill wrote:
Here is another question/comment as I move through this implementation:
I see a strong need for future<void>.
If I build my multi-threaded task scheduling system around future, I will likely have some invocations which do not return a value, but which I do want to synchronize with, receive exceptions from, and possibly cancel().
Has there been any work/thoughts how to handle this? Should future<void> be allowed?
N2185 does include a future<void> specialization.