A modern programming language that makes developers happier.

kotlinlang

In <https://github.com/kevincianfarini/monarch|my project> I’m seeing a pretty strange regression when upgrading to Kotlin 2.1.20-RC. Looks to be a LLVM failure?

```e: Compilation failed: Invalid LLVM module
Verification errors:
    Call parameter type does not match function signature!
      %40 = call zeroext i1 @"kfun:io.github.kevincianfarini.monarch.BooleanFeatureFlag#<get-default>(){}kotlin.Boolean-trampoline"(ptr %39), !dbg !1058
     ptr  %41 = call zeroext i1 @"kfun:kotlin#<Boolean-unbox>(kotlin.Any){}kotlin.Boolean"(i1 %40), !dbg !1058
    Call parameter type does not match function signature!
      %78 = call double @"kfun:io.github.kevincianfarini.monarch.DoubleFeatureFlag#<get-default>(){}kotlin.Double-trampoline"(ptr %77), !dbg !1074
     ptr  %79 = call double @"kfun:kotlin#<Double-unbox>(kotlin.Any){}kotlin.Double"(double %78), !dbg !1074```
Any tips on where to begin debugging this? Everything works fine in Kotlin 2.1.10.

Seems like this issue might be related to <https://youtrack.jetbrains.com/issue/KT-63426|this YouTrack issue>, however I’m not sure why I’m only now experiencing this.

Hey! Could you please provide steps to reproduce the failure?

Thanks! I've reproduced and minimized this, reported as <https://youtrack.jetbrains.com/issue/KT-75483/Native-redundant-unboxing-generated-with-smart-cast>.

The project I linked above reproduces this simply by updating the kotlin version to the RC and running iOS tests. Happy to create a PR if that's helpful?

In the YouTrack filed above it says that 2.1.20-Beta1 is affected but this also affects the RC. 

Do we think this will be something resolved before 2.1.20 final? This OSS project is used in my work project and is preventing us from upgrading.

&gt; The project I linked above reproduces this simply by updating the kotlin version to the RC and running iOS tests. Happy to create a PR if that's helpful?
No, I've already reproduced the issue, so no need for that.

&gt; In the YouTrack filed above it says that 2.1.20-Beta1 is affected but this also affects the RC.
That field basically means that 2.1.20-Beta1 is the first version affected by the problem. It naturally affects all further versions until fixed.

&gt; Do we think this will be something resolved before 2.1.20 final? 
Likely.