Compiling Lambda Expressions: Scala vs. Java 8
Compiling Lambda Expressions: Scala vs. Java 8
Join the DZone community and get the full member experience.Join For Free
Lambda expressions have taken the programming world by storm in the last few years. Most modern languages have adopted them as a fundamental part of functional programming. JVM based languages such as Scala, Groovy and Clojure have integrated them as key part of the language. And now, Java 8 is (finally) joining in on the fun.
What’s interesting about Lambda expressions is that from the JVM’s perspective they’re completely invisible. It has no notion of what an anonymous function or a Lambda expression is. It only knows bytecode which is a strict OO specification. It’s up to the makers of the language and its compiler to work within these constraints to create newer, more advanced language elements.
We first encountered this when we were working on adding Scala support to Takipi and had to dive deep into the Scala compiler. With Java 8 right around the corner, I thought it would be interesting to see how the Scala and Java compilers implement Lambda expressions. The results were pretty surprising.
To get things going I took a simple Lambda expression that converts a list of Strings to a list of their lengths.
In Java -
List names = Arrays.asList("1", "2", "3"); Stream lengths = names.stream().map(name -> name.length());
In Scala -
val names = List("1", "2", "3") val lengths = names.map(name => name.length)
Don’t be tricked its simplicity - behind the scenes some complex stuff is going on.
Let’s start with Scala
I used javap to view the bytecode contents of the .class produced by the Scala compiler. Let’s look at the result bytecode (this is what the JVM will actually execute).
// this loads the names var into the stack (the JVM thinks // of it as variable #2). // It’s going to stay there for a while till it gets used // by the .map function. aload_2
Next, things gets more interesting - a new instance of a synthetic class generated by the compiler is created and initialized. This is the object that from the JVM’s perspective holds the Lambda method. It’s funny that while the Lambda is defined as an integral part of our method, in reality it lives completely outside of our class.
new myLambdas/Lambda1$anonfun$1 // instantiate the Lambda object dup // put it into the stack again // finally, invoke the c’tor. Remember - it’s just a plain object // from the JVM’s perspective. invokespecial myLambdas/Lambda1$anonfun$1/()V // these two (long) lines loads the immutable.List CanBuildFrom factory // which will create the new list. This factory pattern is a part of // Scala’s collections architecture getstatic scala/collection/immutable/List$/MODULE$ Lscala/collection/immutable/List$; invokevirtual scala/collection/immutable/List$/canBuildFrom() Lscala/collection/generic/CanBuildFrom; // Now we have on the stack the Lambda object and the factory. // The next phase is to call the .map() function. // If you remember, we loaded the names var onto // the stack in the beginning. Now it’ll gets used as the // this for the .map() call, which will also // accept the Lambda object and the factory to produce the // new list of lengths. invokevirtual scala/collection/immutable/List/map(Lscala/Function1; Lscala/collection/generic/CanBuildFrom;)Ljava/lang/Object;
But hold on - what’s going on inside that Lambda object?
The Lambda object
The Lambda class is derived from scala.runtime.AbstractFunction1. Through this the map() function can polymorphically invoke the overridden apply() whose code is below -
// this code loads this and the target object on which to act, // checks that it’s a String, and then calls another apply overload // to do the actual work and boxes its return value. aload_0 //load this aload_1 //load the string arg checkcast java/lang/String //make sure it’s a String - we got an Object // call another apply() method in the synthetic class invokevirtual myLambdas/Lambda1$anonfun$1/apply(Ljava/lang/String;)I //box the result invokestatic scala/runtime/BoxesRunTime/boxToInteger(I)Ljava/lang/Integer areturn
The actual code to perform the .length() operation is nested in that additional apply method which simply returns the length of the String as we expected.
Phew.. it was quite a long way to get here :)
aload_1 invokevirtual java/lang/String/length()I ireturn
For a line as simple as we write above, quite a lot of bytecode is generated - an additional class and a bunch of new methods. This of course isn’t meant to dissuade us from using Lambdas (we’re writing in Scala, not C). It just goes to show the complexity behind these constructs. Just think of the amount of code and complexity that goes into compiling complex chains of Lambda expressions!
I was quite expecting Java 8 to implement this the same way, but was quite surprised to see that they took another approach completely.
Java 8 - A new approach
The bytecode here is a bit shorter but does something rather surprising. It begins quite simply by loading the names var and invokes its .stream() method, but then it does something quite elegant. Instead of creating a new object that will wrap the Lambda function, it uses the new invokeDynamic instruction which was added in Java 7 to dynamically link this call site to the actual Lambda function.
aload_1 //load the names var // call its stream() func invokeinterface java/util/List.stream:()Ljava/util/stream/Stream; //invokeDynamic magic! invokedynamic #0:apply:()Ljava/util/function/Function; //call the map() func invokeinterface java/util/stream/Stream.map: (Ljava/util/function/Function;)Ljava/util/stream/Stream;
InvokeDynamic magic. This JVM instruction was added in Java 7 to make the JVM less strict, and allows dynamic languages to bind symbols at run-time, vs. doing all the linkage statically when the code is compiled by the JVM.
Dynamic Linking. If you look at the actual invokedynamic instruction you’ll see there’s no reference of the actual Lambda function (called lambda$0). The answer lies in the way invokedynamic is designed (which in itself deserves a full post), but the short answer is the name and signature of the Lambda, which in our case is -
// a function named lamda$0 that gets a String and returns an Integer lambdas/Lambda1.lambda$0:(Ljava/lang/String;)Ljava/lang/Integer;
are stored in an entry in a separate table in the .class to which the #0 parameter passed to the instruction points. This new table actually changed the structure of the bytecode specification for the first time after a good few years, requiring us to adapt Takipi’s error analysis engine to it as well.
The Lambda code
This is the code for the actual Lambda expression. It’s very cookie-cutter - simply load the String parameter, call length() and box the result. Notice it was compiled as a static function to avoid having to pass an additional this object to it like we saw in Scala.
aload_0 invokevirtual java/lang/String.length:() invokestatic java/lang/Integer.valueOf:(I)Ljava/lang/Integer; areturn
This is another advantage of the invokedynamic approach, as it allows us to invoke the method in a way which is polymorphic from the .map() function’s perspective, but without having to allocate a wrapper object or invoke a virtual override method. Pretty cool!
Summary. It’s fascinating to see how Java, the most “strict” of modern languages is now using dynamic linkage to power its new Lambda expressions. It’s also an efficient approach, as no additional class loading and compilation is needed - the Lambda method is simply another private method in our class.
Java 8 has really done a very elegant job in using new technology introduced in Java 7 to implement Lambda expressions in what is a very straightforward way. It’s pleasant in a way to see that even a “venerable” lady such as Java can teach us all some new tricks :)
Originally appeared in Takipi's Blog
Opinions expressed by DZone contributors are their own.