57

I have a Kotlin interface with a default implementation, for instance:

interface Foo {
    fun bar(): String {
        return "baz"
    }
}

This would be okay until I try to implement this interface from Java. When I do, it says the class need to be marked as abstract or implement the method bar(). Also when I try to implement the method, I am unable to call super.bar().

Vojtěch
  • 11,312
  • 31
  • 103
  • 173
  • 11
    This is a known issue, and is being tracked here: https://youtrack.jetbrains.com/issue/KT-4779 – zsmb13 May 25 '17 at 12:01

5 Answers5

48

Generating true default methods callable from Java is an experimental feature of Kotlin 1.2.40.

You need to annotate the methods with the @JvmDefault annotation:

interface Foo {
    @JvmDefault
    fun bar(): String {
        return "baz"
    }
}

This feature is still disabled by default, you need to pass the -Xjvm-default=enable flag to the compiler for it to work. (If you need to do this in Gradle, see here).

It really is experimental, however. The blog post warns that both design and implementation may change in the future, and at least in my IDE, Java classes are still marked with errors for not implementing these methods, despite compiling and working fine.

Tura
  • 1,227
  • 11
  • 22
zsmb13
  • 85,752
  • 11
  • 221
  • 226
  • This feature is still experimental in 1.2.50 - if using Maven you need to add `1.8` to the `` section of the overall pom and `-Xjvm-default=enable` to the `` section of the `kotlin-maven-plugin`. – George Hawkins Jun 25 '18 at 08:36
  • 1
    At least nowadays the correct argument seems to be `-Xjvm-default=enable` – Paulus Limma Jul 31 '18 at 08:47
  • Can anyone with experience/insight into Kotlin update this to tell us if/when this feature has become "official"? From what I see Kotlin is up to 1.5.x now and [the docs for `JvmDefault`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.jvm/-jvm-default/) don't mention it being experimental. – Joachim Sauer Oct 25 '21 at 12:13
  • 1
    @Joachim Sauer: The `@JvmDefault` annotation is now deprecated, see [the answer](https://stackoverflow.com/a/70956485/1391631) for details. – Tordanik Feb 05 '22 at 12:07
28

Please see the related issue.

There is a recommendation in the comments:

Write your interface in Java (with default methods) and both the Java and Kotlin classes correctly use those defaults

Karatheodory
  • 895
  • 10
  • 16
  • Does it mean that if interface will have optional method then it is better to write it in Java with default keyword for better interoperability? – Bitwise DEVS Oct 08 '22 at 06:29
15

If you know you won't be overriding the function in any implementations of your interface, you can use extension functions as a nice workaround for this issue. Just put an extension function in the same file as the interface (and at the top level so other files can use it).

For example, what you're doing could be done this way:

interface Foo {
    // presumably other stuff
}

fun Foo.bar(): String {
    return "baz"
}

See the docs on extension functions for more information about them.

One "gotcha" worth noting:

We would like to emphasize that extension functions are dispatched statically, i.e. they are not virtual by receiver type. This means that the extension function being called is determined by the type of the expression on which the function is invoked, not by the type of the result of evaluating that expression at runtime.

Put simply, extension functions don't do what you might expect from regular polymorphism. What this means for this workaround is that the default function cannot be overridden like a regular function. If you try to override it, you'll get some weird behavior, because the "overridden" version will be called whenever you're dealing explicitly with the subclass, but the extension version will be called when you're dealing with the interface generically. For example:

interface MyInterface {
    fun a()
}

fun MyInterface.b() {
    println("MyInterface.b() default implementation")
}

class MyInterfaceImpl : MyInterface {
    override fun a() {
        println("MyInterfaceImpl.a()")
    }

    fun b() {
        println("MyInterfaceImpl.b() \"overridden\" implementation")
    }
}

fun main(args: Array<String>) {
    val inst1: MyInterface = MyInterfaceImpl()
    inst1.a()
    inst1.b() // calls the "default" implementation

    val inst2: MyInterfaceImpl = MyInterfaceImpl() // could also just do "val inst2 = MyInterfaceImpl()" (the type is inferred)

    inst2.a()
    inst2.b() // calls the "overridden" implementation
}
drmercer
  • 430
  • 8
  • 11
6

Since Kotlin 1.4.0, you can use one of the following compiler flags:

  • -Xjvm-default=all
  • -Xjvm-default=all-compatibility (for binary compatibility with old Kotlin code)

This will enable JVM default method compilation for all interfaces.

If you want to read up on how to set these flags in your IDE or Maven/Gradle project, check out the documentation on compiler options.

Progress on this is being tracked in issue KT-4779, which also includes a helpful summary of the current state. The @JvmDefault annotation and the older -Xjvm-default=enable and -Xjvm-default=compatibility compiler flags should no longer be used.

Tordanik
  • 1,188
  • 11
  • 29
0

Unlike earlier version of Java8, Kotlin can have default implementation in interface.

When you implement Foo interface into a Java class. Kotlin hides those implementation of interface method. As stated here.

Arrays are used with primitive datatypes on the Java platform to avoid the cost of boxing/unboxing operations. As Kotlin hides those implementation details, a workaround is required to interface with Java code

This is specific for Arrays in above link but it also applies to all the classes (May be to give support for earlier version of Java8).

EDIT

Above explanation is opinion based.

One thing i came across and that is the main reason.

Kotlin binaries were compiled with java bytecode version 1.8 without default methods in interfaces. And they are facing critical issue solving it.

Sachin Chandil
  • 17,133
  • 8
  • 47
  • 65