« Return to Thread: Updated version of futures library
Re: Updated version of futures library
by Frank Mori Hess-2
::
Rate this Message:
On Saturday 31 May 2008 23:21, Frank Mori Hess wrote:
> I don't particularly like the implicit conversion from T to future<T>,
Err, I meant future<T> to T.
> but that has absolutely nothing to do with not wanting to treat a
> future<T> as a placeholder. It's simply because the conversion can
> block, and thus produce unexpected behavior (an object appearing on the
> right hand side of an assignment stalling your program). The explicit
> future::get() at least gives a hint that something more than a quick
> conversion might be happening.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
> I don't particularly like the implicit conversion from T to future<T>,
Err, I meant future<T> to T.
> but that has absolutely nothing to do with not wanting to treat a
> future<T> as a placeholder. It's simply because the conversion can
> block, and thus produce unexpected behavior (an object appearing on the
> right hand side of an assignment stalling your program). The explicit
> future::get() at least gives a hint that something more than a quick
> conversion might be happening.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
attachment0 (196 bytes) « Return to Thread: Updated version of futures library
| Free embeddable forum powered by Nabble | Forum Help |
