-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
Investigate getting rid of the AsyncFn* family of traits in favor of LendingFn* #120694
Copy link
Copy link
Open
Labels
A-async-closures`async || {}``async || {}`C-cleanupCategory: PRs that clean code up or issues documenting cleanup.Category: PRs that clean code up or issues documenting cleanup.C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.T-typesRelevant to the types team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
A-async-closures`async || {}``async || {}`C-cleanupCategory: PRs that clean code up or issues documenting cleanup.Category: PRs that clean code up or issues documenting cleanup.C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.T-typesRelevant to the types team, which will review and decide on the PR/issue.Relevant to the types team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
This will allow us to avoid annoying trait duplication if we want to add
gen ||andasync gen ||closures.We need to lower
impl async Fn()bounds toLendingFnbounds using theassociated_type_boundsfeature. This doesn't work currently until:associated_type_boundsfeature #120584 fixes associated type bounds in some positionsFn/FnMut, or just have two new traits, i.e. figure out how to unify the fact thatLendingFnMutdoesn't necessarily haveFnOnceas a supertrait.