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
This would be convenient for crates which re-export the async_recursion macro, like frameworks whose users need an async_recursion-like macro to function (e.g. to store async functions and closures in a struct).
If the documentation on the macro were on the macro directly, the re-export in dependent crates would show that documentation as well.
The text was updated successfully, but these errors were encountered:
This would be convenient for crates which re-export the async_recursion macro, like frameworks whose users need an async_recursion-like macro to function (e.g. to store async functions and closures in a struct).
If the documentation on the macro were on the macro directly, the re-export in dependent crates would show that documentation as well.
The text was updated successfully, but these errors were encountered: