There is a problem of migrating `-Xlambda=indy` and `-Xjvm-default-all` compilation flags. It seems...

# eap

[altavir]

There is a problem of migrating -Xlambda=indy and -Xjvm-default-all compilation flags. It seems like both are not relevant in K2: https://youtrack.jetbrains.com/issue/KT-46770/Stabilize-JVM-specific-experimental-features, but I can't find any announcement about that.

[udalov]

• In 2.0, the default generation strategy of lambdas was changed to indy. -Xlambdas=indy and -Xlambdas=class are still there, but the default is indy. Announcement is here: https://kotlinlang.org/docs/whatsnew-eap.html#generate-lambda-functions-using-invokedynamic
• There have been no changes to the -Xjvm-default argument, there are still three modes disable, all and all-compatibility, with disable as the default. So maybe you could clarify what you mean by "not relevant"

[altavir]

Which is default for jmv-defaul? Because I got a warning that compiler argument is not needed when I pass it to compilerOptions

[udalov]

There have been no changes to the -Xjvm-default argument, there are still three modes disable, all and all-compatibility, with disable as the default.

[altavir]

Ah, thank you