Review Request: CR#8001634 : Initial set of lambda functional interfaces (original) (raw)
Remi Forax forax at univ-mlv.fr
Sun Nov 4 02:42:30 PST 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/04/2012 11:29 AM, David Holmes wrote:
On 4/11/2012 6:04 AM, Brian Goetz wrote:
Ok, everyone seems ok with procedure, but how much do we actually dislike block? (I think this one is an "ain't broke, don't fix") case, and personally I find procedure buth clunky and more limiting than block (just as factory is more limiting than supplier.).
(Respond only if you hate block.) I find Block devoid of useful information (similar to thunk) it's just a name for a chunk of code. Procedure.apply works better for me. Procedure.apply also (to me) naturally takes arguments and returns nothing.
I prefer Proc to Procedure and Fun to Function. Those functional interfaces will be used frequently like List, Deque or Map are used now, and as you can see the collection framework tends to use short conceptual names, I think we should keep this convention.
David
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