-
Notifications
You must be signed in to change notification settings - Fork 653
adding loop_fn_back in to the future-rs #2444
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
Comments
Quickly reviewing the implementation, you could use |
What is the use case for this? Historically, this function has been removed in favor of In any case, I would like to know about specific use cases that require this. |
there nothing that requires this usage, my only thought is that it could be useful if you didn't want to write a future without using async and await for example purposes! I certainly have no problem with it being under a feature flag for migration |
I would prefer not to add this unless there is a specific use case that requires this. |
I have created a small library that isn't entirely completed but almost there to add loop fn back in,
I wasn't entirely sure how I would alter the mod files to add it in but i think there
the library is at
https://github.com/warlord500/loop_fn_future
The text was updated successfully, but these errors were encountered: