What's New in Java 8
Last updated
Last updated
$7.20Minimum
$14.51Suggested
Add Ebook to Cart
What's New in Java 8
An unofficial guide to Java and JDK 1.8
[](http://creativecommons.org/licenses/by-nc-sa/3.0/deed.en_US) This work is licensed under a [Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License](http://creativecommons.org/licenses/by-nc-sa/3.0/deed.en_US)
Like many Java developers, the first time I heard about lambda expressions it piqued my interest. Also like many others, I was disappointed when it was set back. However, it is better late than never.
Java 8 is a giant step forward for the Java language. Writing this book has forced me to learn a lot more about it. In Project Lambda, Java gets a new closure syntax, method-references, and default methods on interfaces. It manages to add many of the features of functional languages without losing the clarity and simplicity Java developers have come to expect.
Aside from Project Lambda, Java 8 also gets a new Date and Time API (JSR 310), the Nashorn JavaScript engine, and removes the Permanent Generation from the HotSpot virtual machine, among other changes.
I would like to acknowledge the following people for providing valuable resources:
Brian Goetz – “State of the Lambda”
Aleksey Shipilev – jdk8-lambda-samples
Richard Warburton – “Java 8 Lambdas”
Julien Ponge – “Oracle Nashorn” in the Jan./Feb. 2014 issue of Java Magazine.
Venkat Subramaniam – agiledeveloper.com
All of the developers behind Java 8.
The developers of Guava, joda-time, Groovy, and Scala.
This book is a short introduction to Java 8. After reading it, you should have a basic understanding of the new features and be ready to start using it.
This book assumes that you have a good understanding of Java the language and the JVM. If you’re not familiar with the language, including features of Java 7, it might be hard to follow some of the examples.
Java 8 includes the following:
Lambda expressions
Method references
Default Methods (Defender methods)
A new Stream API.
Optional
A new Date/Time API.
Nashorn, the new JavaScript engine
Removal of the Permanent Generation
and more…
The best way to read this book is with a Java 8 supporting IDE running so you can try out the new features.
The biggest new feature of Java 8 is language level support for lambda expressions (Project Lambda). A lambda expression is like syntactic sugar for an anonymous class with one method whose type is inferred. However, it will have enormous implications for simplifying development.
The main syntax of a lambda expression is “parameters -> body”. The compiler can usually use the context of the lambda expression to determine the functional interface being used and the types of the parameters. There are four important rules to the syntax:
Declaring the types of the parameters is optional.
Using parentheses around the parameter is optional if you have only one parameter.
Using curly braces is optional (unless you need multiple statements).
The “return” keyword is optional if you have a single expression that returns a value.
Here are some examples of the syntax:
The last expression could be used to sort a list; for example:
In this case the lambda expression implements the Comparator interface to sort strings by length.
Here’s a short example of using lambdas with the Runnable interface:
The important thing to note is both the r1 and r2 lambdas call the toString() method of the Hello class. This demonstrates the scope available to the lambda.
You can also refer to final variables or effectively final variables. A variable is effectively final if it is only assigned once.
For example, using Spring’s HibernateTemplate:
In the above, you can refer to the variable sql because it is only assigned once. If you were to assign to it a second time, it would cause a compilation error.
Since a lambda expression is like an object-less method, wouldn’t be nice if we could refer to existing methods instead of using a lamda expression? This is exactly what we can do with method references.
For example, imagine you frequently need to filter a list of Files based on file types. Assume you have the following set of methods for determining a file’s type:
Whenever you want to filter a list of files, you can use a method reference as in the following example (assuming you already defined a method getFiles() that returns a Stream):
Method references can point to:
Static methods.
Instance methods.
Methods on particular instances.
Constructors (ie. TreeSet::new)
For example, using the new java.nio.file.Files.lines method:
The above reads the file “Nio.java”, calls trim() on every line, and then prints out the lines.
Notice that System.out::println refers to the println method on an instance of PrintStream.
In Java 8 a functional interface is defined as an interface with exactly one abstract method. This even applies to interfaces that were created with previous versions of Java.
Java 8 comes with several new functional interfaces in the package, java.util.function.
Function<T,R> - takes an object of type T and returns R.
Supplier<T> - just returns an object of type T.
Predicate<T> - returns a boolean value based on input of type T.
Consumer<T> - performs an action with given object of type T.
BiFunction - like Function but with two parameters.
BiConsumer - like Consumer but with two parameters.
It also comes with several corresponding interfaces for primitive types, such as:
IntConsumer
IntFunction<R>
IntPredicate
IntSupplier
The coolest thing about functional interfaces is that they can be assigned to anything that would fulfill their contract. Take the following code for example:
This code is perfectly valid Java 8. The first line defines a function that prepends “@” to a String. The last two lines define functions that do the same thing: get the length of a String.
The Java compiler is smart enough to convert the method reference to String’s length() method into a Function (a functional interface) whose apply method takes a String and returns an Integer. For example:
This would print out the lengths of the given strings.
Any interface can be functional interface, not merely those that come with Java. To declare your intention that an interface is functional, use the @FunctionalInterface annotation. Although not necessary, it will cause a compilation error if your interface does not satisfy the requirements (ie. one abstract method).
To better illustrate the benefit of Lambda-expressions, here are some examples of how code from Java 7 can be shortened in Java 8.
Creating an ActionListener
Printing out a list of Strings
Sorting a list of Strings
Sorting
For the sorting examples, assume you have the following Person class:
Here’s how you might sort this list in Java 7 by last-name and then first-name:
In Java 8, this can be shortened to the following:
This example uses a static method on an interface (comparing) and a default method (thenComparing) which are discussed in the next chapter.
In order to add the stream method (or any others) to the core Collections API, Java needed another new feature, Default methods (also known as Defender Methods or Virtual Extension methods). This way they could add new methods to the List interface for example without breaking all the existing implementations (backwards compatibility).
Default methods can be added to any interface. Like the name implies, any class that implements the interface but does not override the method will get the default implementation.
For example, the stream method in the Collection interface is defined something like the following:
You can always override a default method if you need different behavior.
An interface can have one or more default methods and still be functional.
For example, take a look at the Iterable interface:
It has both the iterator() method and the forEach method.
In the unlikely case that your class implements two or more interfaces that define the same default method, Java will throw a compilation error. You will need to override the method and choose from one of the methods. For example:
In the above code, talk is overridden and calls Foo’s talk method. This is similar to the way you refer to a super class in pre-Java-8.
Although not strictly related to default methods, the ability to add static methods to interfaces is a similar change to the Java language.
For example, there are many static methods on the new Stream interface. This makes “helper” methods easier to find since they can be located directly on the interface, instead of a different class such as StreamUtil or Streams.
Here’s an example in the new Stream interface:
The above method creates a new stream based on the given values.
The Stream interface is such a fundamental part of Java 8 it deserves its own chapter.
The Stream interface is located in the java.util.stream package. It represents a sequence of objects somewhat like the Iterator interface. However, unlike the Iterator, it supports parallel execution.
The Stream interface supports the map/filter/reduce pattern and executes lazily, forming the basis (along with lambdas) for functional-style programming in Java 8.
There are also corresponding primitive streams (IntStream, DoubleStream, and LongStream) for performance reasons.
There are many ways to create a Stream in Java 8. Many of the existing Java core library classes have Stream returning methods in Java 8.
Streaming Collections
The most obvious way to create a stream is from a Collection.
The Collection interface has two default methods on it for creating streams:
stream(): Returns a sequential Stream with the collection as its source.
parallelStream(): Returns a possibly parallel Stream with the collection as its source.
The ordering of the Stream relies on the underlying collection just like an Iterator.
Streaming Files
The BufferedReader now has the lines() method which returns a Stream; for example:
You can also read a file as a Stream using Files.lines(Path filePath); for example:
Note this populates lazily; it does not read the entire file when you call it.
Files.lines(Path): Any IOException that is thrown while processing the file (after the file is opened) will get wrapped in an UncheckedIOException and thrown.
Streaming File Trees
There are several static methods on the Files class for navigating file trees using a Stream.
list(Path dir) – Stream of files in the given directory.
walk(Path dir) – Stream that traverses the file tree depth-first starting at the given directory.
walk(Path dir, int maxDepth) – Same as walk(dir) but with a maximum depth.
Streaming Text Patterns
The Pattern class now has a method, splitAsStream(CharSequence), which creates a Stream.
For example:
The above uses a very simple pattern, a comma, and splits the text into a stream and prints it out. This would produce the following output:
Infinite Streams
Using the generate or iterate static methods on Stream, you can create a Stream of values including never ending streams. For example, you could call generate in the following way to create an infinite supply of objects:
For example, you could use this technique to produce a stream of CPU load or memory usage. However, you should use this with caution. It is similar to an infinite loop.
You could also use generate to create an infinite random number supply; for example:
However, the java.util.Random class does this for you with the following new methods: ints(), longs(), and doubles(). Each of those methods is overloaded with definitions similar to the following:
ints(): An infinite Stream of random integers.
ints(int n, int m): An infinite Stream of random integers from n (inclusive) to m (exclusive).
ints(long size): A Stream of given size of random integers.
ints(long size, int n, int m): A Stream of given size of random integers with given bounds.
The iterate method is similar to generate except it takes an initial value and a Function that modifies that value. For example, you can iterate over the Integers using the following code:
This would print out “1234…” continuously until you stop the program.
There are ways to limit an infinite stream which we will cover later (filter and limit).
Ranges
There are also new methods for creating ranges of numbers as Streams.
For example, the static method, range, on the IntStream interface:
The above would print out the numbers one through ten.
Each primitive Stream (IntStream, DoubleStream, and LongStream) has a corresponding range method.
Streaming Anything
You can create a Stream from any number of elements or an array using the two following methods:
Stream.of can take any number of parameters of any type.
The most basic thing you can do with a Stream is loop through it using the forEach method.
For example, to print out all of the files in the current directory, you could do the following:
For the most part, this replaces the “for loop”. It is more concise, and more object-oriented since you are delegating the implementation of the actual loop.
Lambda expressions and default methods allow us to implement map/filter/reduce in Java 8. Actually it is already implemented for us in the standard library.
For example, imagine you want to get the current point scores from a list of player-names and find the player with the most points. You have a simple class, PlayerPoints, and a getPoints method defined as the following:
Finding the highest player could be done very simply in Java 8 as shown in the following code:
This could also be done in Java 7 with the dollar library (or similarly with Guava or Functional-Java), but it would be much more verbose as shown in the following:
The major benefit to coding this way (apart from the reduction in lines of code) is the ability to hide the underlying implementation of map/reduce. For example, it’s possible that map and reduce are implemented concurrently, allowing you to easily take advantage of multiple processors. We’ll describe one way to do this (ParallelArray) in the following section.
The ParallelArray was part of JSR-166, but ended up being excluded from the standard Java lib. It does exist and was released to the public domain (you can download it from the JSR website).
Although it was already out there, it really wasn’t easy to use until closures were included in the Java language. In Java 7 using the ParallelArray looks like the following:
In Java 8, you can do the following:
However, Java 8’s addition of stream() and parallelStream() make this even easier:
This makes it extremely simple to switch between a sequential implementation and a concurrent one.
You can do something similar to this right now if you use Groovy with the GPars library in the following way:
The static method GParsPool.withPool takes in a closure and augments any Collection with several methods (using Groovy’s Category mechanism). The parallel method actually creates a ParallelArray (JSR-166) from the given Collection and uses it with a thin wrapper around it.
You can peek into a stream to do some action without interrupting the stream.
For example you could print out elements to debug code:
You can use any action you want, but you should not try to modify elements; you should use map instead.
The limit(int n) method can be used to limit a stream to the given number of elements. For example:
The above would print out ten random integers.
Stream also has the sorted() method for sorting a stream. Like all intermediate methods on Stream (such as map, filter, and peek), the sorted() method executes lazily. Nothing happens until a terminating operation (such as reduce or forEach) is called. However, you should call a limiting operation like limit before calling sorted() on an infinite stream.
For example, the following would throw a runtime exception (using build 1.8.0-b132):
However, the following code works just fine:
Also, you should call sorted() after any calls to filter. For example, this code prints out the first five Java file-names in the current directory:
The code above does the following:
Lists the files in the current directory.
Maps those files to file names.
Finds names that end with “.java”.
Takes only the first five (sorted alphabetically).
Prints them out.
Since Streams are lazily evaluated and support parallel execution, you need a special way to combine results; this is called a Collector.
A Collector represents a way to combine the elements of a Stream into one result. It consists of three things:
A supplier of an initial value.
An accumulator which adds to the initial value.
A combiner which combines two results into one.
There are two ways to do this: collect(supplier,accumulator,combiner), or collect(Collector) (types left off for brevity).
Luckily, Java 8 comes with several Collectors built in. Import them the following way:
Simple Collectors
The simplest collectors are things like toList() and toCollection():
Joining
If you’re familiar with Apache Commons’ StringUtil.join, the joining collector is similar to it. It combines the stream using a given delimiter. For example:
This would combine all of the names into one String separated by commas.
Statistics
More complex collectors resolve to a single value. For example, you can use an “averaging” Collector to get the average; for example:
The above code calculates the average length of non-empty lines in the file “Nio.java”.
Sometimes you want to collect multiple statistics about a collection. Because Streams are consumed when you call collect, you need to calculate all of your statistics at once. This is where SummaryStatistics comes in. First import the one you want to use:
Then use the summarizingInt collector; for example:
The above code performs the same average as before, but also computes the maximum, minimum, and count of the elements.
There’s also summarizingLong and summarizingDouble.
Equivalently, you can map your stream to a primitive type and then call summaryStatistics(). For example:
The groupingBy collector groups elements based on a function you provide. For example:
Similarly, the partitioningBy method creates a map with a boolean key. For example:
To execute grouping in parallel (if you don’t care about ordering) you should use the groupingByConcurrent method. The underlying stream should be unordered to allow grouping to occur in parallel; for example: dragons.parallelStream().unordered().collect(groupingByConcurrent(Dragon::getColor));.
To better illustrate the benefit of Streams in Java 8, here are some examples of code from Java 7 compared to their new versions.
Finding a maximum
Calculating an average
Printing the numbers one through ten
Joining Strings
Java 8 comes with the Optional class in the java.util package for avoiding null return values (and thus NullPointerException). It is very similar to Google Guava’s Optional, which is similar to Nat Pryce’s Maybe class and Scala’s Option class.
Tony Hoare, the inventor of null, has gone on record calling it his “billion-dollar mistake”. Despite your opinion of null, many efforts have been made to make null-checks part of the compilation or automated-code-check process; for example, the @Nonnull annotation of JSR-305. Optional makes it very simple for API designers to avoid null.
You can use Optional.of(x) to wrap a non-null value, Optional.empty() to represent a missing value, or Optional.ofNullable(x) to create an Optional from a reference that may or may not be null.
After creating an instance of Optional, you then use isPresent() to determine if the there is a value and get() to get the value. Optional provides a few other helpful methods for dealing with missing values:
orElse(T) – Returns the given default value if the Optional is empty.
orElseGet(Supplier<T>) – Calls on the given Supplier to provide a value if the Optional is empty.
orElseThrow(Supplier<X extends Throwable>) – Calls on the given Supplier for an exception to throw if the Optional is empty.
It also includes functional style (lambda friendly) methods, like the following:
filter(Predicate<? super T> predicate) – Filters the value and returns a new Optional.
flatMap(Function<? super T,Optional<U>> mapper) – Performs a mapping operation which returns an Optional.
ifPresent(Consumer<? super T> consumer) – Executes the given Consumer only if there is a value present (no return value).
map(Function<? super T,? extends U> mapper) – Uses the given mapping Function and returns a new Optional.
The new Stream interface has multiple methods which return Optional (in case there are no values in the Stream):
reduce(BinaryOperator<T> accumulator) – Reduces the stream to a single value.
max(Comparator<? super T> comparator) – Finds the maximum value.
min(Comparator<? super T> comparator) – Finds the minimum value.
Nashorn replaces Rhino as the default JavaScript engine for the Oracle JVM. Nashorn is much faster since it uses the invokedynamic feature of the JVM. It also includes a command line tool (jjs).
JDK 8 includes the command line tool jjs for running JavaScript.
You can run JavaScript files from the command line (assuming you have Java 8’s bin in your PATH):
This can be useful for running scripts; for example, let’s say you wanted to quickly find the sum of some numbers:
Running the above code should print out 27.
Running jjs with the -scripting option starts up an interactive shell where you can type and evaluate JavaScript.
You can also embed variables into strings and have them evaluate; for example:
This would print out the current date and time.
You can also run JavaScript dynamically from Java.
First, you need to import the ScriptEngine:
Second, you use the ScriptEngineManager to get the Nashorn engine:
Now you can evaluate javascript at any point:
The eval method can also take a FileReader as input:
This way you can include and run any JavaScript. However, keep in mind that the typical variables available to you in the browser (window, document, etc.) are not available.
You can import and use Java classes and packages using the JavaImporter.
For example, import java.util, the IO, and NIO file packages:
The above demonstrates that paths is an instance of LinkedList and prints out the list.
Later on you could add the following code to write text into the files:
We can use existing Java classes, but we can also create new ones.
You can extend Java classes and interfaces using the Java.type and Java.extend functions. For example, you can extend the Callable interface and implement the call method:
You can also invoke JavaScript functions directly from Java.
Firstly, you need to cast the engine to the Invocable interface:
Then, to invoke any function, simple use the invokeFunction method, for example:
Lastly, you can use the getInterface method to implement any interface in JavaScript.
For example, if you have the following JPrinter interface, you can use it like so:
Java 8 introduces a new Date/Time API that is thread-safe, easier to read, and more comprehensive than the previous API. Java’s Calendar implementation has not changed much since it was first introduced and Joda-Time is widely regarded as a better replacement. Java 8’s new Date/Time API is very similar to Joda-Time.
The main difference you will notice is that there are several different classes to represent time, date, time period, and timezone specific data. Also there are transformers for dates and times.
For dates and times without a timezone, use the following:
LocalDate – Day, month, year.
LocalTime – Time of day only.
LocalDateTime – Both date and time.
For timezone specific times you use ZonedDateTime.
Previous to Java 8, to calculate the time eight hours in the future you would need to write something like the following:
In Java 8, you can more simply write the following:
There are also well-named methods such as plusDays, plusMonths, minusDays, and minusMonths. For example:
Note that each method returns a different instance of LocalDate. The original LocalDate, today, remains unchanged. This is because the new Date-Time types are immutable. This allows them to be thread-safe and cacheable.
Creating new date and time objects is much easier and less error-prone in Java 8. Every type is immutable and has static factory methods.
For example, creating a new LocalDate for March 15, 2014 is as simple as:
For more type-safety, you can use the new Month enum:
You can also easily create a LocalDateTime by combining an instance of LocalDate with a LocalTime:
You could also use any of the following methods (on LocalDate):
atTime(int hour, int minute)
atTime(int hour, int minute, int second)
atTime(int hour, int minute, int second, int nanoOfSecond)
Every class also has the now() method, which corresponds to the instant (or date) it is called.
Java 8 adds several enums, such as java.time.temporal.ChronoUnit for expressing things like “days” and “hours” instead of the integer constants used in the Calendar API. For example:
There’s also the java.time.DayOfWeek and java.time.Month enums.
The month enum can be used to create LocalDates and is returned by LocalDate::getMonth. For example here is how you might create a LocalDate and print out the month.
This would print out “MARCH”.
The Clock can be used in conjunction with dates and times to help build your tests. During production a normal Clock can be used, and a different one during tests.
To get the default clock, use the following:
The Clock can then be passed into factory methods; for example:
Java 8 has two types for representing time differences as humans understand them, Period and Duration.
Duration is a time-based amount of time, such as ‘34.5 seconds’. Period is a date-based amount of time, such as ‘2 years, 3 months and 4 days’.
Periods and Durations can be determined using the between method:
They can also be created using static methods. For example, Durations can be created for any amount of seconds, minutes, hours, or days:
Periods and Durations can be added or subtracted from Java 8 date types. For example:
A TemporalAdjuster can be used to do tricky date “math” that is popular in business applications. For example they can be used to find the “first Monday of the month” or “next Tuesday”.
The java.time.temporal.TemporalAdjusters class contains a bunch of useful methods for creating TemporalAdjusters. Here are a few of them:
firstDayOfMonth()
firstDayOfNextMonth()
firstInMonth(DayOfWeek)
lastDayOfMont()
next(DayOfWeek)
nextOrSame(DayOfWeek)
previous(DayOfWeek)
previousOrSame(DayOfWeek)
To use a TemporalAdjuster use the with method. This method returns an adjusted copy of the date-time or date object. For example:
The Instant class represents a point in time measured to the nanosecond. It forms the basis of time measurements in the Java 8 date-time API.
Much like the old Date class, Instant measures time starting from the “epoch” (Jan. 1, 1970) and is time-zone ignorant.
Time-Zones are represented by the java.time.ZoneId class. There are two types of ZoneIds, fixed offsets and geographical regions. This is to compensate for things like “daylight saving time” which can be very complex.
You can get an instance of a ZoneId in many ways including the following two:
To print out all available IDs, use getAvailableZoneIds():
The original Date and Calendar objects have the toInstant() method to convert them to the new Date-Time API. You can then use an ofInstant(Insant,ZoneId) method to get a LocalDateTime or ZonedDateTime object; for example:
The proposed implementation will allocate class meta-data in native memory and move interned Strings and class statics to the Java heap. [http://openjdk.java.net/jeps/122]
Most allocations for the class metadata are now allocated out of native memory. This means that you won’t have to set the “XX:PermSize” options anymore (they don’t exist).
This also means that you will get a “java.lang.OutOfMemoryError: Metadata space” error message instead of “java.lang.OutOfMemoryError: Permgen space” when you run out of memory.
This is part of the convergence of the Oracle JRockit and HotSpot JVMs.
Java 8 has tons of new features that you might miss with all of the focus on lambdas. Here are some of them:
java.util.Base64
Cryptography upgrades (lots)
JDBC 4.2
Repeatable Annotations
Annotations on types
For a more complete list, please see the official list.
Until now, Java developers have had to rely on third-party libraries for encoding and decoding Base-64. Since it is such a frequent operation, a large project will typically contain several different implementations of Base64. For example: Apache commons-codec, Spring, and Guava all have separate implementations.
For this reason, Java 8 has java.util.Base64. It acts like a factory for Base64 encoders and decoders and has the following methods:
getEncoder()
getDecoder()
getUrlEncoder()
getUrlDecoder()
Each factory method returns either an Encoder or Decoder.
The URL Base-64 Encoder provides an encoding that is URL and Filename safe (62 is - and 63 is _).
Prior to Java 8, annotations could be used on any declaration. In Java 8, annotations can also be applied to the use of types. Here are some examples:
This new ability is primarily aimed at supporting type-checking frameworks, such as Checker. These frameworks help find errors in your code at compile time.
Java 8 will allow annotations annotated with @Repeatable to be repeated.
For example, let’s say you’re coding a game and want to use annotations to schedule when methods should be called. You can declare multiple schedules using multiple annotations:
For this to be possible, you need to have the following:
The Schedule annotation needs to use the meta-annotation @Repeatable.
There needs to be another annotation as declared by the @Repeatable annotation.
Due to Java’s emphasis on backwards-compatibility, repeating annotations are actually stored within another annotation (that you provide). The @Repeatable annotation takes in a value that is the class of the containing annotation. For example:
Schedule is now a repeatable annotation.
You can use reflection to access repeatable annotations at runtime. To do this there is a new method called getAnnotationsByType(Class annotationClass) on Class, Constructor, Method, etc. It returns an array of all such annotations (or an empty array if there are none).
Java 8 manages to add many of the features of functional languages without significantly changing the Java language.
When lambda expressions, method-references, the Stream interface, and immutable data-structures are combined, Java enables what could be called “functional programming” (FP).
For the purposes of this book, the three pillars of FP are as follows:
Functions
Immutability
Concurrency
Of course, as the name implies, functional programming is based on functions as a first-class feature. Java 8 arguably elevates functions to a first-class feature with the Lambda Project and functional interfaces.
The Function interface (and related interfaces IntFunction, DoubleFunction, LongFunction, BiFunction, etc.) represents the compromise made by Java 8 in elevating functions to objects. This interface allows functions to be passed as arguments, stored as variables, and be returned by methods.
The Function interface has the following default methods:
andThen(Function): Returns a composed function that first applies this function to its input, and then applies the given function to the result.
compose(Function): Similar to andThen but in reversed order (first applies the given function to its input, and then this function).
identity(): Returns a function that always returns its input argument.
You can use these methods to create a chain for creating a function; for example:
The resulting function would take an Integer, multiply it by two, and then prepend “str” to it.
You can use andThen any number of times to create a single function. Also, remember that functions can be passed and returned from methods. Here’s an example involving the new Date-Time API:
This method would take in a function that operates on a LocalDate and convert it into a function that returns a LocalDateTime (with a time of 2:02am).
Tuples
If you need a functional interface for a method with more than two parameters (eg. “TriFunction”) you need to make it yourself or use a library. Another way to handle this issue is to use a data structure called a Tuple.
A Tuple is a typed data structure for holding a number of elements. Some languages, such as Scala, have built-in support for Tuples. Tuples are useful whenever you are handling multiple related values, but don’t want all of the overhead of creating a new class.
Here’s a very simple example of implementing a Tuple with two elements:
Tuples also allow you to approximate returning multiple values.
In functional programming, state is considered harmful and avoided whenever possible. Instead, immutable (unchangeable) data structures are preferred. For example, String is an immutable type in Java.
As you may have learned, Java 8’s new Date-Time classes are immutable. What you may not have realized is that almost everything added in Java 8 is immutable (Optional and Streams for example).
However, you need to be careful when using Java 8’s new functional patterns to not accidentally fall back into the mutable mind-set. For example, the following type of code should be avoided:
You may think you are being clever, but this kind of thing can cause problems. Instead, you should do something like the following:
If you ever find yourself resorting to mutability, consider if you could use some combination of “filter”, “map”, “reduce” or “collect” instead.
With the increasing popularity of multi-core processors, concurrent programming has become more important. Functional programming forms a solid basis for concurrent programming and Java 8 supports concurrency in many different ways.
One of those ways is the parallelStream() method on Collection. It provides a very quick way to use a Stream concurrently. However, like all optimizations, you should test to make sure that your code is actually faster, and it should be used sparingly. Too much concurrency could actually cause your application to slow down.
Another way Java 8 supports concurrency is with the new CompletableFuture class. It has the supplyAsync static method that takes in the functional interface Supplier. It also has the method thenAccept which takes in a Consumer that handles completion of the task. The CompletableFuture calls on the given supplier in a different thread and executes the consumer when complete.
When used in conjunction with things like the CountDownLatch, AtomicInteger, AtomicLong, AtomicReference, … you can implement thread-safe, concurrent FP-like code; for example:
This example finds the closest dragon to a certain Location (assume that Dragon’s distance method involves a time-consuming calculation).
However, this could be simplified using the parallelStream() default method (since only one type of calculation is going on) in the following way:
This performs essentially the same task as the previous example but in a more concise (and functional) way.
One of the hallmarks of functional programming is tail-call recursion. It solves the same problem as iteration (which does not exist in FP). Unfortunately, it can cause stack-overflows if not properly optimized by the compiler.
Tail-Call optimization refers to when a compiler converts a recursive function call into a loop to avoid using the call stack. For example, a function that uses tail-call recursion in Lisp will be automatically optimized this way.
Java 8 does not support tail-call optimization like some other languages (yet). However, it is possible to approximate it using something like the following interface:
The Tail interface has three default methods and one abstract-method (apply). The invoke() method contains the meat of the “tail-call optimization”:
It takes advantage of Stream’s iterate method to create an infinite Stream which will continuously call Tail’s apply method.
Then it uses filter and findFirst to stop the Stream when isDone() returns true.
Finally, it returns the result.
To implement the “done” condition, there is the following additional static method on Tail:
With the Tail interface you can mimic tail-call recursion quite easily in Java 8. Here’s an example of calculating factorial using this interface (using BigInteger so that very large factorials can be computed):
Using this method, you can make extremely fast programs while still maintaining the functional style.
Of course the JVM does a lot optimization by itself, so this may not always be the best course. However, it is something to keep in mind.
In this particular case, a simple recursive factorial is faster than the code above, however it causes a StackOverflowError for sufficiently large numbers whereas streamFactorial does not.
Thank you for reading this short introduction to Java 8. Hopefully you learned a lot and are ready to starting using it yourself.
To recap, Java 8 includes the following:
Lambda expressions
Method references
Default Methods (Defender methods)
A new Stream API.
Optional
A new Date/Time API.
Nashorn, the new JavaScript engine
Removal of the Permanent Generation
To keep track of possible future features of Java, you might want to look at JEPS.
If for some reason you can’t immediately upgrade to Java 8, there are some ways to backport some Java 8 features to previous versions.
For each of the following features, here is the backport or similar library:
Lambdas – Retrolambda
Lazily Evaluated Sequences – totallylazy
Optional – guava
Date/Time – ThreeTen
Nashorn – nashorn-backport
Use the backports with caution.
Code examples can be found on .
See the for more information.
See for more examples.
See for more on Spliterators.
There are several implementations of Tuples available in Java, such as and .
