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
Promise.then() is difficult to use with lambdas #165
Comments
|
That's a good point @sclassen. This is the right time to provide an alias and deprecate filter or do a full rename given that we're braking binary compatibility. |
My proposal for renaming (based on the naming in java streams and vavr.io): The code would then read as follows:
|
I get |
yes. Does this explanation help? |
* Provide aliases for filter/pipe. Fix for #165 * Fully rename pipe/filter methods instead of providing aliases
Currently
Promise.then
takes 3 different types of inputs:DoneCallback
,DoneFilter
, andDonePipe
. This forces explicit casts when using lambda expressions. It would be better if this method were to be split in 3 variants, such asThe text was updated successfully, but these errors were encountered: