-
Notifications
You must be signed in to change notification settings - Fork 142
The finally() operator #129
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
Conversation
|
In Promise implementations like reactphp or sabre this is typically called |
|
@martinsik This is a If we want to stick to RxJS naming, @felixfbecker |
|
@martinsik it looks like there is a line break issue with the error demo with hhvm: https://travis-ci.org/ReactiveX/RxPHP/jobs/194568201#L341-L350 |
|
|
|
Just to clarify, I'm only suggesting the name change for RxPHP v1x. I think that |
|
Aren't all other |
|
I would go with |
|
I think @felixfbecker has a good point. Isn't this going to be confusing when we'll have |
|
Just to move things along - I change my vote to |
|
Ok, so I'll call it |
This is the
finally()operator based on its RxJS 5 implementation. I called infinallyCall()here becausefinallyis a keyword but in RxPHP 2 I'll rename it to justfinally().