Request for Review (#2) : CR#8001634 : Initial set of lambda functional interfaces (original) (raw)

Doug Lea dl at cs.oswego.edu
Wed Nov 14 15:51:52 PST 2012

On 11/14/12 12:29, Tim Peierls wrote:

Implementing more than one of the functional interfaces sounds like a bad idea; making it difficult or impossible to do is a *good *thing. Use apply everywhere to prevent things like Shimmer implements FloorWax, DessertTopping.

Does anyone have any compelling example of why you actually might want to implement multiple functional interfaces that isn't satisfied by using asFunction, asPredicate, asProcedure, etc. methods?

I see how/why people might need to do this, but I also think that if JDK sets a precedent of relentlessly calling every method "apply" then others will follow, and so there won't be all that much need for such adaptors anyway.

So I'm still in the "apply, the ultimate functional method name" camp.

-Doug

More information about the lambda-libs-spec-observers mailing list