11 Aug
2007
11 Aug
'07
9:36 p.m.
On Friday 10 August 2007 21:13, Peter Dimov wrote:
There's a discussion on the committee -lib reflector at the moment which has raised an interesting point: if no futures remain, it might be desirable (in some cases) to cancel the thread that is executing the task as nobody is listening for the result.
I personally like being able to "fire and forget" without having to keep the future around to prevent the asyncronous function call from cancelling itself. Especially in the case of a future<void> return value. -- Frank