[
https://issues.apache.org/jira/browse/MESOS-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15225735#comment-15225735
]
Gilbert Song commented on MESOS-5038:
-------------------------------------
Thanks [~haosd...@gmail.com], I like this idea, and definitely we need it.
Thanks for putting this as the first on your patches chain.
Just want to discuss: `any` sounds good to me, but will we possibly have a more
accurate name for this mechanism?
> Added a any mechanism for futures
> ---------------------------------
>
> Key: MESOS-5038
> URL: https://issues.apache.org/jira/browse/MESOS-5038
> Project: Mesos
> Issue Type: Improvement
> Components: libprocess
> Reporter: haosdent
> Assignee: haosdent
>
> Now we already have {{collect}} and {{await}} mechanisms which would wait for
> a list of {{Future}}. However, we would like to return immediately if any of
> the list of {{Future}} complete instead of wait for the whole list finished
> in {{collect}}. The interface of this any mechanism could be
> {code}
> template <typename T>
> Future<T> any(const std::list<Future<T>>& futures);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
