Review Request: CR#8001634 : Initial set of lambda functional interfaces (original) (raw)
Brian Goetz brian.goetz at oracle.com
Thu Nov 1 07:16:46 PDT 2012
- Previous message: Review Request: CR#8001634 : Initial set of lambda functional interfaces
- Next message: Review Request: CR#8001634 : Initial set of lambda functional interfaces
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
And this is made worse by the fact that Mapper becomes the de-facto "Function" (or maybe this is the central problem with it; if it were used only in map(...) calls you probably wouldn't have noticed.)
On the other end of the spectrum, I am still pretty negative on "Fun" and "Function" for reasons we've already discussed.
So, what are the alternatives in the middle that might work?
Transform(er) Project{ion,or} more?
On 11/1/2012 7:58 AM, Doug Lea wrote:
http://cr.openjdk.java.net/~mduigou/8001634/2/webrev/
My main non-technical reaction is that more I see "Mapper", the more I hate it. It interacts awfully especially with Maps. "Fun" (with lots of precedent in other languages) would be fine. Even "Function" would be fine. -Doug
- Previous message: Review Request: CR#8001634 : Initial set of lambda functional interfaces
- Next message: Review Request: CR#8001634 : Initial set of lambda functional interfaces
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the lambda-libs-spec-observers mailing list