You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
Similar to #405's addition of
Future::race
we should exposeFuture::join
andFuture::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 aboutFuture::join
vsFuture::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!
The text was updated successfully, but these errors were encountered: