Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Method References Cannot Always Replace Lambda Expressions

DZone's Guide to

Method References Cannot Always Replace Lambda Expressions

Make sure you keep your types, arguments, and signatures straight. While method references can sometimes replace lambdas, they can't always make them work.

· Java Zone
Free Resource

Just released, a free O’Reilly book on Reactive Microsystems: The Evolution of Microservices at Scale. Brought to you in partnership with Lightbend.

A couple of weeks ago, I gave one of my "Writing awesome Java code" workshops. While I was explaining ways of designing APIs using lambda expressions, a participant asked a question that I couldn't answer. There was a simple lambda expression in the example code, and the question was if it could be replaced with a method reference. I agreed and changed it to a method reference. However, the code didn't compile. That confused me, of course. After having thought for a while, the answer came to me — and it's pretty simple.  In this article, I want to share my insights.

There are two simple methods, one without any parameters, one with exactly one parameter:

private int methodWithoutParameter() {
    return 0;
}

/**
* Equals exactly method signature of java.util.function.Function:apply
*/
private int methodWithParameter(int x) {
    return x;
}


The following test documents that the lambda expression in line 15 cannot be replaced with the method reference in line 16. The reason for this is that the lambda expression is of the same signature than the required function, which needs one Integer parameter "in" and one Integer as a return value. However, the lambda ignores the "in" parameter because methodWithoutParameter() is called without using k at all. That works fine for the lambda. However, the method reference needs the exact signature and doesn't work otherwise.

@Test
public void methodReferencesCannotAlwaysReplaceLambdas() {

    Map<Integer, Integer> myMap = new HashMap<>();

    // Both lambda and method reference can be used to implement Function, if the method signature equals
    // signature of java.util.function.Function::apply:
    Function<Integer, Integer> functionWithParameter1 = (k) -> methodWithParameter(k);
    Function<Integer, Integer> functionWithParameter2 = this::methodWithParameter;
    myMap.computeIfAbsent(2, functionWithParameter1);
    myMap.computeIfAbsent(2, functionWithParameter2);
    functionWithParameter1.apply(5);

    // Only lambda can be used to implement Function if the method signature differs from the right signature:
    Function<Integer, Integer> functionWithoutParameter1 = k -> methodWithoutParameter();
    Function<Integer, Integer> functionWithoutParameter2 = this::methodWithoutParameter; // not possible
    myMap.computeIfAbsent(2, functionWithoutParameter1);
    functionWithoutParameter1.apply(5);
}


So, what can be expressed with a lamba cannot be necessarily expressed with a method reference.

Strategies and techniques for building scalable and resilient microservices to refactor a monolithic application step-by-step, a free O'Reilly book. Brought to you in partnership with Lightbend.

Topics:
java ,method references ,lambda expressions ,functional programming ,tutorial

Published at DZone with permission of Steven Schwenke. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}