Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wait_any/wait_all are badly named #500

Closed
stevenrbrandt opened this issue Aug 20, 2012 · 2 comments
Closed

wait_any/wait_all are badly named #500

stevenrbrandt opened this issue Aug 20, 2012 · 2 comments

Comments

@stevenrbrandt
Copy link
Member

The functions wait_any and wait_all are badly named, as they do not wait. Possibly when_all or when_any would be better names.

@hkaiser
Copy link
Member

hkaiser commented Aug 21, 2012

We already renamed wait_all to when_all and wait_any to when_any and re-added wait_all/wait_any with different semantics, e.g. actually waiting (see 76b4811).

This is still non-satisfactory, as when is now used with two different semantics: future<>::when attaches a continuation, while when_all/when_any are used to combine other asynchronous operations.

@ghost ghost assigned hkaiser Feb 2, 2013
@hkaiser
Copy link
Member

hkaiser commented Feb 2, 2013

I think this can be closed as future::when has already been renamed to future::then.

@hkaiser hkaiser closed this as completed Feb 2, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants