-
Notifications
You must be signed in to change notification settings - Fork 26.3k
Add done() API to Future #42013
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
Add done() API to Future #42013
Conversation
[ghstack-poisoned]
[ghstack-poisoned]
💊 CI failures summary and remediationsAs of commit 716aefd (more details on the Dr. CI page): 💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.Please report bugs/suggestions on the GitHub issue tracker or post in the (internal) Dr. CI Users group. This comment has been revised 12 times. |
Differential Revision: [D22729596](https://our.internmc.facebook.com/intern/diff/D22729596) [ghstack-poisoned]
Differential Revision: [D22729596](https://our.internmc.facebook.com/intern/diff/D22729596) [ghstack-poisoned]
rohan-varma
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! For the annotation, is there any way to test/validate it (such as running mypy typechecker)?
I believe there are tests to cover this. The first version caused test failures, as I was using |

Stack from ghstack:
Differential Revision: D22729596