Skip to content

Consider removing join3/4/5 #2215

@taiki-e

Description

@taiki-e

I'd prefer removing join3/4/5 (and try_join3/4/5) in futures 0.4, for the following reasons:

The only downside is it cannot store the returned future in a struct without unstable features, but few people actually do it with (try_)join3/4/5.

Related: #1742

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-futureArea: futures::future

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions