Request for Review (#2) : CR#8001634 : Initial set of lambda functional interfaces
Mike Duigou
mike.duigou at oracle.com
Tue Nov 13 15:28:22 PST 2012
They won't be truly final until JSR-335 is ratified but they are more fixed than placeholders.
Brian has provided some feedback for Block method name and some suggestions for naming of primitive specialization. I plan make those changes today and send out RFR #3 tomorrow around noon PST.
Feedback is always welcome but it's the EG that needs to be convinced a change is warranted.
Mike
On Nov 13 2012, at 14:56 , Stephen Colebourne wrote:
> On 13 November 2012 19:05, Mike Duigou <mike.duigou at oracle.com> wrote:
>> I've updated the webrev for the first set of lambda functional interfaces (JSR-335) with the feedback from the first review round. The updated webrev is:
>>
>> http://cr.openjdk.java.net/~mduigou/8001634/3/webrev/
>>
>> This update includes:
>>
>> - Mapper.map becomes Function.apply
>> - Factory.make becomes Supplier.get
>> - Specializations of Supplier for int, long, double
>> - Reorder type variables to put result last
>> - Fixes many javadoc and stylistic comments.
>>
>> What didn't change:
>> - Block was not renamed to Action or Procedure. The name Block.apply currently conflicts with Function.apply and should be renamed. Block.accept? Block.perform?
>> - Combiner will be part of the full API but it's only present in this patch as a comment.
>> - No default methods.
>
> Can you confirm whether these are now considered to be the final
> naming choices, or whether they are still (improved) placeholders.
> Stephen
More information about the lambda-dev
mailing list