-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
feat: narrow ResultInterface to concrete implementation after calling isSucceeded()
and isFailed()
#466
Conversation
Pull Request Test Coverage Report for Build 8735731205Details
💛 - Coveralls |
… `isSucceeded()` and `isFailed()`
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.
Thanks for the PR.
Seems like a nice addition!
… `isSucceeded()` and `isFailed()` (azjezz#466)
I think we need to revert this 😅 repro:
|
Hm, that's true. 😢2 Should I send revert PR? |
Woops, merged a bit too fast - sorry. |
… calling `isSucceeded()` and `isFailed()` (azjezz#466)" This reverts commit d211454.
There u go #469 |
BTW is there any chance the RFC is accepted in the future? (like it was missing something that could be fixed) |
No description provided.