apply

[Brian Goetz]

>> And here's where there might be some good news for you. Since we
>> currently have
>>
>>    interface UnaryOperator<T> extends Function<T,T>
>>
>> then it actually is quite reasonable for UnaryOperator to adopt the
>> name from
>> Function, since there is no way to implement UnaryOperator without
>> implementing
>> Function.  In which case some of the offenders -- Unary/BinaryOperator
>> -- can go
>> away.
>
> Please.
>
> Also, it is amusing that in current lambda repo,
> Block has accept but BiBlock has apply. That's the one
> that led to my "OMG I gotta stop this nonsense!" posting.

Yeah, that's just a typo that's going to get fixed.