Functional (SAM) interfaces
An interface with only one abstract method is called a functional interface, or a Single Abstract Method (SAM) interface. The functional interface can have several non-abstract members but only one abstract member.
To declare a functional interface in Kotlin, use the
For functional interfaces, you can use SAM conversions that help make your code more concise and readable by using lambda expressions.
Instead of creating a class that implements a functional interface manually, you can use a lambda expression. With a SAM conversion, Kotlin can convert any lambda expression whose signature matches the signature of the interface's single method into the code, which dynamically instantiates the interface implementation.
For example, consider the following Kotlin functional interface:
If you don't use a SAM conversion, you will need to write code like this:
By leveraging Kotlin's SAM conversion, you can write the following equivalent code instead:
A short lambda expression replaces all the unnecessary code.
You can also use SAM conversions for Java interfaces.
Migration from an interface with constructor function to a functional interface
Starting from 1.6.20, Kotlin supports callable references to functional interface constructors, which adds a source-compatible way to migrate from an interface with a constructor function to a functional interface. Consider the following code:
With callable references to functional interface constructors enabled, this code can be replaced with just a functional interface declaration:
Its constructor will be created implicitly, and any code using the
::Printer function reference will compile. For example:
Preserve the binary compatibility by marking the legacy function
Printer with the
@Deprecated annotation with
Functional interfaces vs. type aliases
You can also simply rewrite the above using a type alias for a functional type:
However, functional interfaces and type aliases serve different purposes. Type aliases are just names for existing types – they don't create a new type, while functional interfaces do. You can provide extensions that are specific to a particular functional interface to be inapplicable for plain functions or their type aliases.
Type aliases can have only one member, while functional interfaces can have multiple non-abstract members and one abstract member. Functional interfaces can also implement and extend other interfaces.
Functional interfaces are more flexible and provide more capabilities than type aliases, but they can be more costly both syntactically and at runtime because they can require conversions to a specific interface. When you choose which one to use in your code, consider your needs:
If your API needs to accept a function (any function) with some specific parameter and return types – use a simple functional type or define a type alias to give a shorter name to the corresponding functional type.
If your API accepts a more complex entity than a function – for example, it has non-trivial contracts and/or operations on it that can't be expressed in a functional type's signature – declare a separate functional interface for it.