Heads up: Mapper<T, R> -> Mapper<R, T>

[Mike Duigou]

The discussions are completely public. What Paul (Sandoz) is referring to is the review of the initial set of functional interfaces which includes this change. The currently ongoing review is being conducted on both the lambda-libs-spec-experts list and lambda-dev lists simultaneously.

http://mail.openjdk.java.net/pipermail/lambda-libs-spec-experts/
http://mail.openjdk.java.net/pipermail/lambda-dev/

The discussion begins with:

http://mail.openjdk.java.net/pipermail/lambda-dev/2012-October/006406.html
http://mail.openjdk.java.net/pipermail/lambda-libs-spec-experts/2012-October/000236.html

Paul Sandoz's patch just makes the lambda workspace consistent with the currently being reviewed material by re-ordering the type parameters.

Mike

On Nov 6 2012, at 07:49 , Paul Benedict wrote:

> Community question: Why aren't the EG discussions public yet? I thought the
> latest JCP brings transparency to the expert list. Is it because lambda is
> not running under the latest JCP transparency rules yet?
> 
> Paul
> 
> On Tue, Nov 6, 2012 at 9:42 AM, Paul Sandoz <paul.sandoz at oracle.com> wrote:
> 
>> Hi,
>> 
>> To align better with EG discussions some nominal function types, such as
>> Mapper/FlatMapper, were modified such that the type parameter for the
>> return type is declared first rather than last.
>> 
>> This is unlikely to affect code using such function types implicitly, i.e.
>> lambda expressions, but will definitely affect code that explicitly depends
>> on such types.
>> 
>> I will endeavour to communicate such changes more quickly in the future.
>> 
>> Paul.
>> 
>> http://hg.openjdk.java.net/lambda/lambda/jdk/rev/e60b1819b652
>> 
>> 
>