Home > Articles > Programming > Java

Interfaces and Lambda Expressions in Java

In this chapter from Core Java for the Impatient, you will learn about interfaces and lambda expressions, including static and default methods, method and constructor references, processing lambda expressions, variable scope, higher-order functions, and local inner classes.
This chapter is from the book

This chapter is from the book

Topics in This Chapter

  • 3.1 Interfaces
  • 3.2 Static and Default Methods
  • 3.3 Examples of Interfaces
  • 3.4 Lambda Expressions
  • 3.5 Method and Constructor References
  • 3.6 Processing Lambda Expressions
  • 3.7 Lambda Expressions and Variable Scope
  • 3.8 Higher-Order Functions
  • 3.9 Local Inner Classes
  • Exercises

Java was designed as an object-oriented programming language in the 1990s when object-oriented programming was the principal paradigm for software development. Interfaces are a key feature of object-oriented programming: They let you specify what should be done, without having to provide an implementation.

Long before there was object-oriented programming, there were functional programming languages, such as Lisp, in which functions and not objects are the primary structuring mechanism. Recently, functional programming has risen in importance because it is well suited for concurrent and event-driven (or “reactive”) programming. Java supports function expressions that provide a convenient bridge between object-oriented and functional programming. In this chapter, you will learn about interfaces and lambda expressions.

The key points of this chapter are:

  • An interface specifies a set of methods that an implementing class must provide.
  • An interface is a supertype of any class that implements it. Therefore, one can assign instances of the class to variables of the interface type.
  • An interface can contain static methods. All variables of an interface are automatically static and final.
  • An interface can contain default methods that an implementing class can inherit or override.
  • The Comparable and Comparator interfaces are used for comparing objects.
  • A lambda expression denotes a block of code that can be executed at a later point in time.
  • Lambda expressions are converted to functional interfaces.
  • Method and constructor references refer to methods or constructors without invoking them.
  • Lambda expressions and local inner classes can access effectively final variables from the enclosing scope.

3.1 Interfaces

An interface is a mechanism for spelling out a contract between two parties: the supplier of a service and the classes that want their objects to be usable with the service. In the following sections, you will see how to define and use interfaces in Java.

3.1.1 Declaring an Interface

Consider a service that works on sequences of integers, reporting the average of the first n values:

public static double average(IntSequence seq, int n)

Such sequences can take many forms. Here are some examples:

  • A sequence of integers supplied by a user
  • A sequence of random integers
  • The sequence of prime numbers
  • The sequence of elements in an integer array
  • The sequence of code points in a string
  • The sequence of digits in a number

We want to implement a single mechanism for deal with all these kinds of sequences.

First, let us spell out what is common between integer sequences. At a minimum, one needs two methods for working with a sequence:

  • Test whether there is a next element
  • Get the next element

To declare an interface, you provide the method headers, like this:

public interface IntSequence {
    boolean hasNext();
    int next();

You need not implement these methods, but you can provide default implementations if you like—see Section 3.2.2, “Default Methods,” on p. 100. If no implementation is provided, we say that the method is abstract.

The methods in the interface suffice to implement the average method:

public static double average(IntSequence seq, int n) {
    int count = 0;
    double sum = 0;
    while (seq.hasNext() && count < n) {
        sum += seq.next();
    return count == 0 ? 0 : sum / count;

3.1.2 Implementing an Interface

Now let’s look at the other side of the coin: the classes that want to be usable with the average method. They need to implement the IntSequence interface. Here is such a class:

public class SquareSequence implements IntSequence {
    private int i;

    public boolean hasNext() {
        return true;

    public int next() {
        return i * i;

There are infinitely many squares, and an object of this class delivers them all, one at a time.

The implements keyword indicates that the SquareSequence class intends to conform to the IntSequence interface.

This code get the average of the first 100 squares:

SquareSequence squares = new SquareSequence();
double avg = average(squares, 100);

There are many classes that can implement the IntSequence interface. For example, this class yields a finite sequence, namely the digits of a positive integer starting with the least significant one:

public class DigitSequence implements IntSequence {
    private int number;

    public DigitSequence(int n) {
        number = n;

    public boolean hasNext() {
        return number != 0;

    public int next() {
        int result = number % 10;
        number /= 10;
        return result;

    public int rest() {
        return number;

An object new DigitSequence(1729) delivers the digits 9 2 7 1 before hasNext returns false.

3.1.3 Converting to an Interface Type

This code fragment computes the average of the digit sequence values:

IntSequence digits = new DigitSequence(1729);
double avg = average(digits, 100);
    // Will only look at the first four sequence values

Look at the digits variable. Its type is IntSequence, not DigitSequence. A variable of type IntSequence refers to an object of some class that implements the IntSequence interface. You can always assign an object to a variable whose type is an implemented interface, or pass it to a method expecting such an interface.

Here is a bit of useful terminology. A type S is a supertype of the type T (the subtype) when any value of the subtype can be assigned to a variable of the supertype without a conversion. For example, the IntSequence interface is a supertype of the DigitSequence class.

3.1.4 Casts and the instanceof Operator

Occasionally, you need the opposite conversion—from a supertype to a subtype. Then you use a cast. For example, if you happen to know that the object stored in an IntSequence is actually a DigitSequence, you can convert the type like this:

IntSequence sequence = ...;
DigitSequence digits = (DigitSequence) sequence;

In this scenario, the cast was necessary because rest is a method of DigitSequence but not IntSequence.

See Exercise 2 for a more compelling example.

You can only cast an object to its actual class or one of its supertypes. If you are wrong, a compile-time error or class cast exception will occur:

String digitString = (String) sequence;
    // Cannot possibly work—IntSequence is not a supertype of String
RandomSequence randoms = (RandomSequence) sequence;
    // Could work, throws a class cast exception if not

To avoid the exception, you can first test whether the object is of the desired type, using the instanceof operator. The expression

object instanceof Type

returns true if object is an instance of a class that has Type as a supertype. It is a good idea to make this check before using a cast.

if (sequence instanceof DigitSequence) {
    DigitSequence digits = (DigitSequence) sequence;

3.1.5 Extending Interfaces

An interface can extend another, providing additional methods on top of the original ones. For example, Closeable is an interface with a single method:

public interface Closeable {
    void close();

As you will see in Chapter 5, this is an important interface for closing resources when an exception occurs.

The Channel interface extends this interface:

public interface Channel extends Closeable {
    boolean isOpen();

A class that implements the Channel interface must provide both methods, and its objects can be converted to both interface types.

3.1.6 Implementing Multiple Interfaces

A class can implement any number of interfaces. For example, a FileSequence class that reads integers from a file can implement the Closeable interface in addition to IntSequence:

public class FileSequence implements IntSequence, Closeable {

Then the FileSequence class has both IntSequence and Closeable as supertypes.

3.1.7 Constants

Any variable defined in an interface is automatically public static final.

For example, the SwingConstants interface defines constants for compass directions:

public interface SwingConstants {
    int NORTH = 1;
    int NORTH_EAST = 2;
    int EAST = 3;

You can refer to them by their qualified name, SwingConstants.NORTH. If your class chooses to implement the SwingConstants interface, you can drop the SwingConstants qualifier and simply write NORTH. However, this is not a common idiom. It is far better to use enumerations for a set of constants; see Chapter 4.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020