Anthony Williams-4 wrote:
I was talking about future operators. That is the composite future we got from f1 || f2, not selecting the first one which is ready. This should become ready when it has an evaluated value of true or false.
Are you envisaging "f1 || f2" as a short-hand for "f1.get() || f2.get()" that may not need to wait for both? I see that as very limited utility, since it only works for future<R> where R can be used with ||.
My "f1 || f2" is a future operator that returns a composite future. It is the future that is subject to ||, not the returned value.
I see. As others has pointed out, maybe we shouldn't supply the operators because of this possible confusion. Johan -- View this message in context: http://www.nabble.com/-future--Early-draft-of-wait-for-multiple-futures-inte... Sent from the Boost - Dev mailing list archive at Nabble.com.