getOrElse is causing the JVM to crash - https://youtrack.jetbrains.com/issue/KT-29242

[dashfwd]

Running this code causes the JVM to crash:

    val some10 = Some(10)
    val some11 = some10.map { it + 1 }

    // if present, this next line with cause the crash
    some11.getOrElse { Some(0) }

The crash is this:

Error: Unable to initialize main class dashfwd.CrashDemoKt
Caused by: java.lang.VerifyError: Bad type on operand stack
Exception Details:
  Location:
    dashfwd/CrashDemoKt.main([Ljava/lang/String;)V @103: invokestatic
  Reason:
    Type 'java/lang/Object' (current frame, stack[0]) is not assignable to 'arrow/core/Option'

Full code to reproduce is available at https://github.com/dashfwd/arrow_crash

This is using:

• MacOS 10.14.6
• Kotlin 1.3.41 (seems to happen with other versions too)
• Open JDK version 12.0.2 (also happens with OpenJDK 11.0.2)

[pakoito]

This is a defect on the Kotlin inliner. On the next release we're not inlining getOrElse anymore. Meanwhile try a clean build and report the error to Jetbrains.

[dashfwd]

Thanks. A clean build didn't seem to impact things, I'll report it to JetBrains.

[dashfwd]

FYI: Looks like getOrElse isn't inlined:
fun <T> Option<T>.getOrElse(default: () -> T): T = fold({ default() }, ::identity)

fold() is though:

  inline fun <R> fold(ifEmpty: () -> R, ifSome: (A) -> R): R = when (this) {
    is None -> ifEmpty()
    is Some<A> -> ifSome(t)
  }

[dashfwd]

JetBrains issue link: https://youtrack.jetbrains.com/issue/KT-33054

[danimontoya]

Without targeting:

compileKotlin {
         kotlinOptions.jvmTarget = "1.8"
}

everything seems fine.. but when targeting 1.8 there are many problems with inline functions

Cannot inline bytecode built with JVM target 1.8 into bytecode that is being built with JVM target 1.6. Please specify proper '-jvm-target' option

[aballano]

According to https://youtrack.jetbrains.com/issue/KT-29242 this is a bug in the language itself, so nothing specific to Arrow itself.

I guess we should revisit this when they release and we bump to Kotlin 1.3.70.

[frikit]

Bug fixed in kotlin 1.3.70+, tested in https://github.com/dashfwd/arrow_crash with 1.3.70 is working fine

I think the issue can be closed now