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

Add Future::join and Future::try_join #470

Closed
yoshuawuyts opened this issue Nov 7, 2019 · 2 comments
Closed

Add Future::join and Future::try_join #470

yoshuawuyts opened this issue Nov 7, 2019 · 2 comments
Labels
api design Open design questions good first issue Good for newcomers

Comments

@yoshuawuyts
Copy link
Contributor

Similar to #405's addition of Future::race we should expose Future::join and Future::try_join as well. However unlike #405 we would keep the macro around because it's the only way of creating a variable-sized tuple when joining multiple results ("return-type polymorphism").

This would be a chance as well to update the future module-level docs to talk about Future::join vs Future::race, making it more symmetrical.

This should be a fun challenge to pick up for whoever is interested. Marking it as "good first issue". Thanks!

@richard-uk1
Copy link

I think this issue has been resolved?

@yoshuawuyts
Copy link
Contributor Author

@derekdreery indeed it is. Thanks for pointing it out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api design Open design questions good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants