You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all Krossbow interfaces still use the old scheme generating a DefaultImpls class with default implementations as static methods. This is not ideal, and we should eventually move to real JVM default methods (since we target JDK8+).
However, this change is binary incompatible, so we should keep generating the old DefaultImpls classes. This is what the -Xjvm-default=all-compatibility mode is for.
Currently all Krossbow interfaces still use the old scheme generating a
DefaultImpls
class with default implementations as static methods. This is not ideal, and we should eventually move to real JVM default methods (since we target JDK8+).However, this change is binary incompatible, so we should keep generating the old
DefaultImpls
classes. This is what the-Xjvm-default=all-compatibility
mode is for.https://blog.jetbrains.com/kotlin/2020/07/kotlin-1-4-m3-generating-default-methods-in-interfaces
The text was updated successfully, but these errors were encountered: