-
Notifications
You must be signed in to change notification settings - Fork 20
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
Make never propagate #30
Comments
I believe it's mostly true: I'd thought about detecting never and short circuiting in merge/all/settle (I think I even wrote the code for it at some point), and I still think it's a pretty cool idea. I ended up believe that real world usages of |
Yes, real-world usages of |
That's an interesting question. I hadn't even considered it :) Now I'm wondering what that would look like ... any chance you've tried it? |
I mean something like
|
never()
claims to "consume virtually no resources". However, this is no more true if never is used in any combinator, especially merge/all/settle. Should we detect nevers, and futures that eventually resolve to a never there and set the result accordingly?If we want to do that, any ideas about the how? Should
Action
implement anonNever
handler that is called byNever::_runAction
?The text was updated successfully, but these errors were encountered: