Review Request: CR#8001634 : Initial set of lambda functional interfaces (original) (raw)
Remi Forax forax at univ-mlv.fr
Thu Nov 1 05:13:10 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 ]
On 11/01/2012 12:58 PM, 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.
I agree with Doug, my students have less problem with filter/Predicate/test than with map/Mapper/map, so instead of map/Mapper/map, map//Fun/apply is in my opinion better, but requires to rename Block.apply to by example Block.execute.
I also think that UnaryOperator and BinaryOperator are name that are too long, I think that Op and BinOp are better.
and BTW, UnaryOperator should extends Mapper<T,T> and not Map<T,T> is currently suggested in the comment of the declaration of UnaryOperator.
-Doug
Rémi
- 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