DZone
Java Zone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
  • Refcardz
  • Trend Reports
  • Webinars
  • Zones
  • |
    • Agile
    • AI
    • Big Data
    • Cloud
    • Database
    • DevOps
    • Integration
    • IoT
    • Java
    • Microservices
    • Open Source
    • Performance
    • Security
    • Web Dev
DZone > Java Zone > How Lambdas And Anonymous Inner Classes Work

How Lambdas And Anonymous Inner Classes Work

Anonymous Inner Classes and lambdas have some similarities, but their differences are important to know if you're going to use them in your work.

Martin Farrell user avatar by
Martin Farrell
·
Feb. 08, 17 · Java Zone · Tutorial
Like (31)
Save
Tweet
53.26K Views

Join the DZone community and get the full member experience.

Join For Free

At first glance, a lambda looks like a shorthand version of an anonymous inner class. But they are not. Today, we'll cover the differences between lambdas and AICs

Key Points

  • Lambdas implement a functional interface.
  • Anonymous Inner Classes can extend a class or implement an interface with any number of methods.
  • Variables – Lambdas can only access final or effectively final.
  • State – Anonymous inner classes can use instance variables and thus can have state, lambdas cannot.
  • Scope – Lambdas can't define a variable with the same name as a variable in enclosing scope.
  • Compilation – Anonymous compiles to a class, while lambda is an invokedynamic instruction.

How They Work

Anonymous Inner Classes (AICs)

  • The compiler generates a class file for each anonymous inner class.
    • For example – AnonymousInnerClass$1.class
  • Like all classes, it needs to be loaded and verified at startup.

Lambdas

The key to lambda implementation is the InvokeDynamic instruction, introduced in Java 7. This allows dynamic languages to bind to symbols at runtime.

A lambda works like this:

  • Generates invokedynamic call site and uses a lambdafactory to return the functional implementation.
  • Lambda converted to a method to be invoked by invokedynamic.
  • The method is stored in a class as a private static method.
  • There are two lambda types. Non-capturing lambdas only use fields inside their bodies, whereas capturing lambdas access fields outside their bodies.

Non-Capturing Lambdas

Doesn't access fields outside its body:

public class NonCapturingLambda {     
  public static void main(String[] args) {        
    Runnable nonCapturingLambda = () -> System.out.println("NonCapturingLambda");        
    nonCapturingLambda.run();     
  } }

If we decode the class file using the CFR decompiler, we see the:

  • LambdaMetafactory
  • Lambda is a static void method in our class
java -jar cfr_0_119.jar NonCapturingLambda --decodelambdas false 
/*  * Decompiled with CFR 0_119.  */ 
import java.io.PrintStream; 
import java.lang.invoke.LambdaMetafactory; 
public class NonCapturingLambda {     
    public static void main(String[] args) {         
        Runnable nonCapturingLambda = (Runnable)LambdaMetafactory.metafactory(null, 
           null, null, ()V, lambda$0(), ()V)();        
        nonCapturingLambda.run();     
    }     

    private static /* synthetic */ void lambda$0() 
    {         System.out.println("NonCapturingLambda");     
    } 
}

Capturing Lambdas

Accesses final or effectively final fields outside their bodies:

public class CapturingLambda {     
    public static void main(String[] args) 
    {         
        String effectivelyFinal = "effectivelyFinal";         
        Runnable capturingLambda = () -> System.out.println("capturingLambda " + effectivelyFinal);         
        capturingLambda.run();     } 
}

This decompiles to:

java -jar cfr_0_119.jar CapturingLambda --decodelambdas false 
/*  * Decompiled with CFR 0_119.  */ 
import java.io.PrintStream; 
import java.lang.invoke.LambdaMetafactory; 
public class CapturingLambda {     
    public static void main(String[] args) {        
        String effectivelyFinal = "effectivelyFinal";         
        Runnable capturingLambda = 
          (Runnable)LambdaMetafactory.metafactory(null, null, null, ()V, 
                                                  lambda$0(java.lang.String ), 
                                                  ()V)((String)effectivelyFinal); 
          capturingLambda.run();     
    }     
    private static /* synthetic */ void lambda$0(String string) {         
        System.out.println("capturingLambda " + string);     
    } 
}

The interesting part is that the lambda$0 method signature has gone from empty to taking a parameter String.

Published at DZone with permission of Martin Farrell, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Anatomy of a Webhook HTTP Request
  • Remote Debugging and Developer Observability
  • Build a Data Pipeline on AWS With Kafka, Kafka Connect, and DynamoDB
  • Event-Driven Hello World Program

Comments

Java Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • MVB Program
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends:

DZone.com is powered by 

AnswerHub logo