Function parameter order (original) (raw)

Remi Forax forax at univ-mlv.fr
Wed Nov 7 07:06:07 PST 2012

On 11/07/2012 04:02 PM, Raab, Donald wrote:

+1

+1 too, it seems that scala, guava and C# uses the same convention, I don't see why we should have a different one.

Rémi

From:lambda-libs-spec-experts-bounces at openjdk.java.net [mailto:lambda-libs-spec-experts-bounces at openjdk.java.net] *On Behalf Of *Kevin Bourrillion Sent: Tuesday, November 06, 2012 11:59 AM To: lambda-libs-spec-experts at openjdk.java.net Subject: Function parameter order

It sounds as though we're planning on Function<ReturnType, InputType>. I'd just like to note that this is going to put codebases that are in any stage of migration to JDK types from existing libraries including Guava in a really, really bad position. Every time I see Function<A, B> for /years/, I am going to have to check the imports to find out whether that's A->B or B-A. I'm not saying this consideration should trump all others. Just noting that I see this as a very bad problem for my user base. -- Kevin Bourrillion | Java Librarian | Google, Inc. |kevinb at google.com <mailto:kevinb at google.com>

More information about the lambda-libs-spec-observers mailing list