-
Notifications
You must be signed in to change notification settings - Fork 134
Async/Await/Futures #49
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
This was mentioned before here. I was thinking of starting on this, after we've tackled other high-priority issues. |
The comment mentioned C async ops, which are only a part of the picture, and I'm not sure they can be used now with futures because there's currently no way to tell if the operation has finished. The main goal I had in mind with raising this issue question was first to discuss whether it makes sense to change the standard Box APIs, like get, put, delete, etc to returning |
How about the observer ops? Could those help? |
Async methods like find() is a highly required feature. |
Looking at some other dart code I've got an impression the API should be asynchronous (returning Futures). Thoughts?
The text was updated successfully, but these errors were encountered: