-
Notifications
You must be signed in to change notification settings - Fork 229
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
Implement async API's as generators instead of using callbacks #87
Comments
Yes! ❤️ |
Hmm, how would we handle |
An exception would be thrown for that case. |
+1 :) |
👍 |
Haven't had the bandwidth to focus on this. Let's re-evaluate this down the road. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Basically like the
*Sync
API's, but using generators instead, so we don't have to loop through every match if we want to stop early. This will also means that we could get rid of all the*Sync
API's.If we some of the async functions actually runs async*, we may want to use Promises as they are really nice instead of the current needed callback hell.
* So that the output of the following code is
1 3 2
:Before:
After:
The text was updated successfully, but these errors were encountered: