-
Notifications
You must be signed in to change notification settings - Fork 124
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
overload transform / transformToUni / transformToMulti #318
Comments
I faced the same issue over the weekend! So +1. |
But it's not really a transform anymore, it's more a replace. |
Indeed |
@gavinking would |
That kinda reflects a bit of a deeper confusion over the organization of these methods. See the discussion in #319. I think we need to clarify our thinking on exactly how the names map to semantics. One could, for example, make the same criticism of one of the overloads of |
I'm collecting thoughts regarding #319 👍 |
and forget this, because it clashes for the compiler |
I'm moving the discussion to #319 |
It's annoying that the
UniOnItem.transformXxxxx()
methods don't have overloaded versions that acceptSupplier
instead ofFunction
, just likecall()
already does.(By adding these overloads we alleviate the need for
v
orignore
parameters in the argument anonymous functions.)The text was updated successfully, but these errors were encountered: